Implementing Accessibility for the Web Platform Martin Robinson - - PowerPoint PPT Presentation

implementing accessibility for the web platform
SMART_READER_LITE
LIVE PREVIEW

Implementing Accessibility for the Web Platform Martin Robinson - - PowerPoint PPT Presentation

Implementing Accessibility for the Web Platform Martin Robinson 2019 Web Engines Hackfest The web is for everyone. Accessibility is useful for everyone. Accessibility is (increasingly) the law. Assistive Technologies Screen reader


slide-1
SLIDE 1

Implementing Accessibility for the Web Platform

Martin Robinson 2019 Web Engines Hackfest

slide-2
SLIDE 2

The web is for everyone.

slide-3
SLIDE 3

Accessibility is useful for everyone.

slide-4
SLIDE 4
slide-5
SLIDE 5

Accessibility is (increasingly) the law.

slide-6
SLIDE 6
slide-7
SLIDE 7

Assistive Technologies

  • Screen reader
  • Braille displays
  • On-screen keyboards
  • Magnifiers
  • Debug inspectors
slide-8
SLIDE 8

Architecture

Web Browser Accessibility APIs Assistive Technology Process Boundary

slide-9
SLIDE 9

Web Browser Architecture

Layout Tree Accessibility Tree Platform A11y APIs

slide-10
SLIDE 10

Platform Interface - Queries

  • Structure of accessibility tree
  • Object dimensions and positions
  • Role of accessibility objects
  • Properties of nodes
  • Text content of node
  • Cursor and selection information
  • Structure of tables
slide-11
SLIDE 11

Platform Interface - Actions

  • Activate links and other interface elements
  • Open and traverse menus
  • Select menu options
  • Change cursor position or selection
  • Scroll browser window
  • Scroll an element into view.
slide-12
SLIDE 12

Chromium Specific Details

Accessibility Tree Accessibility Tree’ Tree Comparison Platform A11y APIs

Events

slide-13
SLIDE 13

Platform Interface - Events

  • Cursor and selection changes
  • Node focus changes
  • Window activation changes
  • Parent or children of node changes
  • Node property and attribute changes
slide-14
SLIDE 14

What are we doing?

  • Implementing this for Chromium and ATK
  • Lots of connecting Chromium interfaces to platform interfaces
  • Accessibility on the Linux desktop is divided into two pieces

○ ATK: Server-side ○ AT-SPI2: Client-side ○ (meaning of server and client are reversed relative to common browser meaning)

  • Mapping between browser roles and platform roles is specified!
  • Look for it in upcoming Chromium releases
slide-15
SLIDE 15

Questions?