# Evolve's accessibility compliance (WCAG / Section 508) **URL:** \ **Category:** FAQ\ **Tags:** accessibility\ **Created:** [November 13, 2017, 10:30am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33 "2017-11-13T10:30:12Z")\ **Posts on this page:** 10\ **Page:** 1
**Author:** ![appitierre](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/appitierre/32/10_2.png) [@appitierre](https://community.evolveauthoring.com/u/appitierre)\ **Post date:** [November 13, 2017, 10:30am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/1 "2017-11-13T10:30:12Z")
Evolve 4 is focused on Accessibility and helping you publish courses that are WCAG/Section 508 compliant. To achieve full compliance in your published Evolve courses please follow the relevant guidelines when developing your courses. [https://www.w3.org/TR/WCAG/](https://www.w3.org/TR/WCAG/) [https://www.section508.gov/](https://www.section508.gov/) ### Screen reader support We have increased support for a number of major screen reader tools that are free. We think Accessible content should be available to all and not cost. Published Evolve 4 content supports the following screen readers: - [NVDA](https://www.nvaccess.org/) - [Chromevox for Chrome browser](https://chrome.google.com/webstore/detail/chromevox/kgejglhpjiefppelpmljglcjbhoiplfn?hl=en) - [Voiceover for Apple OSX](https://www.apple.com/uk/accessibility/mac/vision/) ### Style the focus outline colour When using tab to navigate a course it may help to change the colour of the outline of items which have been tabbed to. This is now possible in Evolve 4. ### Extended Aria label support Aria label support allows course developers to customise what content screen readers read out and gives much greater control when developing accessible eLearning content. We’ve extended Aria label support across the following Extensions, Menus and Components. ---
**Author:** ![Gareth\_Walker](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/gareth_walker/32/242_2.png) [@Gareth\_Walker](https://community.evolveauthoring.com/u/Gareth_Walker)\ **Post date:** [August 23, 2018, 10:43am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/2 "2018-08-23T10:43:00Z")
There has been an accessibility release since this FAQ. Does that mean Evolve is now compliant with these standards – so long as content creators adhere to good practice, etc.? ---
**Author:** ![appitierre](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/appitierre/32/10_2.png) [@appitierre](https://community.evolveauthoring.com/u/appitierre)\ **Post date:** [August 28, 2018, 6:56am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/3 "2018-08-28T06:56:34Z")
@Gareth_Walker It has indeed - more detail here - [https://www.appitierre.com/blog/evolve-4-release-accessibility/](https://www.appitierre.com/blog/evolve-4-release-accessibility/) ---
**Author:** ![appitierre](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/appitierre/32/10_2.png) [@appitierre](https://community.evolveauthoring.com/u/appitierre)\ **Post date:** [August 28, 2018, 6:58am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/4 "2018-08-28T06:58:13Z")
Evolve 4 is focused on Accessibility and helping you publish courses that are WCAG/Section 508 compliant. To achieve full compliance in your published Evolve courses please follow the relevant guidelines when developing your courses. [https://www.w3.org/TR/WCAG/](https://www.w3.org/TR/WCAG/) [https://www.section508.gov/](https://www.section508.gov/) ### Screen reader support We have increased support for a number of major screen reader tools that are free. We think Accessible content should be available to all and not cost. Published Evolve 4 content supports the following screen readers: - [NVDA](https://www.nvaccess.org/) - [Chromevox for Chrome browser](https://chrome.google.com/webstore/detail/chromevox/kgejglhpjiefppelpmljglcjbhoiplfn?hl=en) - [Voiceover for Apple OSX](https://www.apple.com/uk/accessibility/mac/vision/) ### Style the focus outline colour When using tab to navigate a course it may help to change the colour of the outline of items which have been tabbed to. This is now possible in Evolve 4. ### Extended Aria label support Aria label support allows course developers to customise what content screen readers read out and gives much greater control when developing accessible eLearning content. We’ve extended Aria label support across the following Extensions, Menus and Components. ---
**Author:** ![Steve](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Steve](https://community.evolveauthoring.com/u/Steve)\ **Post date:** [August 29, 2018, 1:43pm UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/5 "2018-08-29T13:43:03Z")
Hi. Does this mean that Evolve doesn’t support the JAWS screen reader? S ---
**Author:** ![appitierre](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/appitierre/32/10_2.png) [@appitierre](https://community.evolveauthoring.com/u/appitierre)\ **Post date:** [August 29, 2018, 2:27pm UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/6 "2018-08-29T14:27:18Z")
Hello @Steve, Our clients use it, but we haven’t tested it. If you find any issues please let us know. Evolve Content is compliant so if it works with one tool it should work with all, unless that tool is not following the compliance or has specific requirements not in the specification. JAWS is widely used but we wanted Evolve to work with as many inclusive free tools as possible, so we haven’t looked specifically at individual companies with paid options. ---
**Author:** ![Steve](https://avatars.discourse-cdn.com/v4/letter/s/f19dbf/32.png) [@Steve](https://community.evolveauthoring.com/u/Steve)\ **Post date:** [August 30, 2018, 1:03am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/7 "2018-08-30T01:03:01Z")
Cool, thanks for the update. ---
**Author:** ![NickEastham](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.evolveauthoring.com/nickeastham/32/1215_2.png) [@NickEastham](https://community.evolveauthoring.com/u/NickEastham)\ **Post date:** [July 22, 2019, 2:56pm UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/8 "2019-07-22T14:56:33Z")
Something that puzzles me is, since NVDA, and indeed most screen readers read out the HTML text anyway, what happens when that text has also been added as ARIA labels? In experimenting with this, the screen reader reads the screen content twice if the ARIA labels have been filled. This isn’t ideal, so I wondered what your advice would be. When should you fill in the ARIA label fields and when should you leave them blank. Thanks, Nick ---
**Author:** ![anon81750324](https://avatars.discourse-cdn.com/v4/letter/a/a88e57/32.png) [@anon81750324](https://community.evolveauthoring.com/u/anon81750324)\ **Post date:** [July 22, 2019, 3:21pm UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/9 "2019-07-22T15:21:51Z")
Hey Nick, This is subjective and entirely down to editor choice. ARIA labels are great for describing what is coming next to a screen reader. Often the common mistake is to fill out the ARIA label the same text as the title. It will just read this out twice because it’s the same text. I rarely recommend filling out Aria labels for things like the text component. Where ARIA labels are useful is for things like Flip Cards. Filling out the ARIA label with something like ‘There are 4 objects to interact with, which will reveal more text when interacted with’. This tells the end user that they have to actually do something to read out the text on the other side. This is also good to have in an ARIA label as this might be different to instructional text, which would normally be something like ‘Flip over each card’ - This wouldn’t make a lot of sense someone visually impaired, as they don’t know how many things to flip over, or where the interactivity ends. Indeed, Evolve will instruct the screen reader to skip this content if it doesn’t have an Aria label filled out - Make sure you check the help text on the ARIA labels for certain interactions. Cheers Wes ---
**Author:** ![danjonesbrightwave](https://avatars.discourse-cdn.com/v4/letter/d/5daacb/32.png) [@danjonesbrightwave](https://community.evolveauthoring.com/u/danjonesbrightwave)\ **Post date:** [September 4, 2019, 8:28am UTC](https://community.evolveauthoring.com/t/evolves-accessibility-compliance-wcag-section-508/33/10 "2019-09-04T08:28:17Z")
> [@anon81750324](#): > > ARIA labels are great for describing what is coming next to a screen reader. Often the common mistake is to fill out the ARIA label the same text as the title. It will just read this out twice because it’s the same text. I rarely recommend filling out Aria labels for things like the text component. > > Where ARIA labels are useful is for things like Flip Cards. Filling out the ARIA label with something like ‘There are 4 objects to interact with, which will reveal more text when interacted with’. This tells the end user that they have to actually do something to read out the text on the other side. This is also good to have in an ARIA label as this might be different to instructional text, which would normally be something like ‘Flip over each card’ - This wouldn’t make a lot of sense someone visually impaired, as they don’t know how many things to flip over, or where the interactivity ends. > > Indeed, Evolve will instruct the screen reader to skip this content if it doesn’t have an Aria label filled out - Make sure you check the help text on the ARIA labels for certain interactions. Hi Evolve, We’ve recently run into some issues with JAWS screen reader and ARIA labels, specifically on Mozilla. Just seeing if this is on the roadmap to be supported? Or, if there are any workarounds in the mean time?