HTML5 Help features that are not 508 compliant

[lp_tw]

I've been trying to figure out which Help features do not meet 508 accessibility requirements and should not be used in projects that must meet those requirements. Below I've listed the features I think need my group needs to avoid. Please let me know if you agree, and if you can think of other features that fall into this category. Features to avoid: Drop-down text, Expanding text, Togglers, Links and cross-references that open in a popup window, the glossary feature (both the left-pane glossary tab and any popups/expanding text in topics), Related Topics links that open as a popup (OK if they appear as a list). This is for HTML5 Help output.

[Carolyn]

Have you discovered any new information since writing this post, or does MadCap have anything to say about this? I'm new to using Flare. My help content must be 508 compliant, and today I've discovered that my related topic link and the popup menu (and the new browswer window that opens upon topic selection!) are not compliant. I came across your post while looking for information on possible settings or other solutions. If it turns out that all these other items you've listed in your post will not work in my help system, my client is going to be disappointed when I tell them. Especially togglers. This is not good news for me.

[sdcinvan]

What is happening with HTML5 output that is 508 compliant?

This section of the online documentation appears to imply that MadCap Flare is 'sort of' 508 compliant:
http://webhelp.madcapsoftware.com/flare ... hlight=508

I say 'sort of' because of this statement, "the runtime and navigation are Section 508 compliant."

I am about to do some preliminary testing. Will there be any surprises?

[sdcinvan]

I dug a little deeper...

Here is a chart:
http://webhelp.madcapsoftware.com/flare ... Output.htm

[sdcinvan]

Just tested my HTML5 document output with http://www.powermapper.com/products/sor ... on-508.htm and found a very large number of errors. Some of them are fixable (my own errors) but others may due to Flare.

I'll do more testing this evening.

[M_Mercer2015]

Any updates on this? My content must be 508 compliant as well.

[dpcremin]

This is a big issue for us as well. I really like Flare and the toolset, but if we cant better 508 compliance it could be a show stopper. Are 508 improvements on the roadmap?

[Nita Beck]

This is a big issue for us as well. I really like Flare and the toolset, but if we cant better 508 compliance it could be a show stopper. Are 508 improvements on the roadmap?

Hi. Welcome to the forums!

Most of the folks around here, including the MVPs, are not MadCap employees, so we're all very unlikely to know what plans MadCap has in store for Flare enhancements. Furthermore, even if anyone did know, I would lay money on the table that they are under a MadCap nondisclosure agreement and so would not comment on future enhancements.

I suggest that you put in a feature request to MadCap re improving the 508 compliance of the output it generates. The more of us who push MadCap on this, the more attention MadCap will give it.

[M_Mercer2015]

Thanks, Nita. In the last month I've put in multiple feature requests and bug reports about 508 compliance issues.