Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Accessibility #2566

merged 49 commits into from Apr 7, 2015

Accessibility #2566

merged 49 commits into from Apr 7, 2015


Copy link

Merging on 7th of April. Get your complaints in BEFORE then.

Based on the notes at:

Designed to resolve: #1803

  • Use Alt Keys to Access Editbar
  • Use Arrow keys to Navigate Editbar
  • Use Alt Keys to access Chat etc.
  • Provide a usable screen reader experience (ARIA specs) (Mostly for visually impaired hombres)
  • Provide fonts suitable for dyslexic users

New tasks as per:

  • Make Timeslider Accessible
  • Show users part is not intuitive
  • Additional Keypresses need to be documented in the WIki
  • Hover on buttons is not consistent due to new titles
  • Pressing on Import/Export button seems to lose focus
  • Make Alt C work from anywhere
  • Alt F9 should only work WITH Alt key
  • Make Escape & Alt Keys work from anywhere (not just pad)
  • Ensure left/right arrow keys don't steal focus when on inputs.
  • High Contrast UI - Available through ep_themes
  • Include Open Dyslexic - "Enable Dyslexic(lulz) friendly font" (prolly a pluigin)
  • Fix Good/Bad & Smiley face instead of Good/Bad - Click event with more info including reading score etc. (Blahblahbblahbhlalalalal)
  • Allow left-right arrow keys to cycle from start > end > start again infinitely.
  • Orca and FF 3.14 says the name of the element on focus <-- I run unity which doesn't allow Orca to be easily updated. I might have to resolve this bug once Orca stable lands on Ubuntu unless someone can jump in and resolve that runs Gnome 3 <-- getting a VM to help w/ this -- Orca test is on hold, doing JAWS first.
  • Can't return to pad from Timeslider
  • Use Control Shift 2 instead of Alt Shift A
  • Provide a nice experience for Showing Authors of a line (curent MVP uses Ctrl-Shift-2, try this!)
  • Test with JAWS
  • Write tests for keystrokes -- Is this possible? Looks like it might just be! (see bold.js)
  • Provide in app documentation?
  • Change Font on Timeslider
  • High Contrast on Timeslider (ep_themes)
  • Put some Aria feedback type values on the timeslider so when a revision is moved backwards/forward the screen reader speaks the new revision value and date/time. Also consider putting aria values on the pad contents so the pad contents is spoken to the reader..


@JohnMcLear JohnMcLear changed the title Accessibility progress Accessibility Mar 25, 2015
Copy link
Member Author

Please note Alt A is now Alt Shift A as per

Copy link
Member Author

Thinking this for a setting:*4QM6Tc6smxr9IWR-.png

On by default

"Keyboard shortcuts" would be a page to a rendered tab of HTML page w/ accessibility controls on built from the Wiki?

Although a user would need to know Alt F9 to get to them so that wouldn't work..

What about a link in the default pad text that points to accessibility? Would only be useful on first pad creation/load and not to pads that have modified contents...

Copy link
Member Author

Alt Shift A is now Control Shift 2...

JohnMcLear added a commit that referenced this pull request Apr 7, 2015
@JohnMcLear JohnMcLear merged commit a534552 into develop Apr 7, 2015
@muxator muxator deleted the editbar-accessibility branch November 30, 2019 23:23
@muxator muxator restored the editbar-accessibility branch December 7, 2019 18:05
@rhansen rhansen deleted the editbar-accessibility branch December 28, 2020 02:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

Improve accessibility for blind people and other users of screen readers
2 participants