** Using WeBWorK **

Imho it's not ideal if the problem code gets into specific output formats, like HTML. Even if HTML is the predominant output mode. For example, you can end up making a problem that you come to realize can't really/easily be made equivalently for PDF hardcopy. And there are other output formats too...

But one option is that you can directly add HTML using MODES(). Like:

TEXT(MODES(HTML=>'<h2>...</h2>'));

or

BEGIN_TEXT

\{MODES(HTML=>'<h2>...</h2>');\}

END_TEXT

or

BEGIN_PGML

[@ MODES(HTML=>'<h2>...</h2>'); @]*

END_PGML

or

$myh2 = MODES(HTML=>'<h2>...</h2>');

and use $myh2 later.

Another option would be to write a macro for this purpose that handles all output modes in sensible ways. For example, headers.pl could be a macro library file with defining a command with syntax like header('Table of Probabilities for Problems 6.1b – 6.1d', 2);

(Except in this case you either want to avoid those explicit numbers, or reference the problem number from the environment variables.)

Just as aside, but I question if putting an h2 in a place like this is really in the best interests of the screen reader user. Where would they jump to next if they are jumping waypoints like this? Is there any content immediately following the table? If so, the label could mislead the person to think there is only a table there and nothing else. Unless you put yet another header immediately following the table.

"Of course webwork can manage that." :-)!

##############################################################
#
# Text
#
#

TEXT("<h2>Table of Probabilities for Problems 6.1b – 6.1d</h2>");

Context()->texStrings;
BEGIN_TEXT

\{TEXT("<h2>Table of Probabilities for Problems 6.1b – 6.1d</h2>")," "\}

END_TEXT

BEGIN_PGML
In pgml use @ signs:
[@ "<h2>Table of Probabilities for Problems 6.1b – 6.1d</h2>" @]*
END_PGML
Context()->normalStrings;