Picture of Oliver Foster
Re: 508 accessibility
by Oliver Foster - Thursday, 10 June 2021, 6:56 AM

> how to bring the focus on text blocks and other course elements with tab press ,space and with other buttons as per WCAG guidelines shortcuts

You've misunderstood the guidlines, you've mixed keyboard accessibility with screen reader accessibility. 

Guidlines are here https://www.w3.org/WAI/WCAG21/quickref/

You probably want to experiment with a screen reader. NVDA is the most used open source screen reader, https://www.nvaccess.org/download/

Screen readers give you an extra cursor that you move with up/down/left/right arrows and a series of other shortcut keys to read the text onscreen. NVDA shortcut keys https://webaim.org/resources/shortcuts/nvda

Keyboard accessibility is, without a screen reader, when you tab/space/enter through just focusable elements, like links, buttons, form inputs, etc. You would not tab to text.

Adapt Framework v2 used to allow tabbing through the text to meet accessibility requirements. In Adapt Framework v4 we shifted to meet the WCAG guidlines by working better with the screen readers. It made the experiences much nicer.