Hi everyone, I’m Yi-Hao. Today I will share our project.
Say it all: Feedback for Improving Non-Visual Presentation Accessibility
This work was collaborate with Joon, and advised by
Jeff and Amy.
Presenters often do not describe the content on their slides.
here’s an example
(The presenter speaking) Anyway, so we did the study and you know basically the audio captcha are
a lot harder.
Not surprising.
So the presenter didn't describe his slide, which include
a graph and study information like the number of participants,
which in this case was 162.
When presenters do not describe the content on their slides
people who are blind and visually impaired will miss out
on information in the presentation, making it inaccessible.
But how often do speaker fail to fully describe their slides in practice?
To find out we analyzed 90 presentation videos
in-the-wild. The video clips contained 269 slides, and 615 total
slide elements — half of which were text and the other
half are media.
Two people coded the speaker verbal coverage of each slide
elements of non, little, half, most, and complete.
Overall, presenter didn't fully describe their slides, leaving
out key information for about 72% of slide elements.
When presenters are explicitly trying to create an accessible
presentation, they can use guidelines, like those from W3C or
SIGACCESS
They suggest that speakers should describe all pertinent
visual information on their slides and use minimal visuals.
However, it can still be challenging for presenters to remember
to describe their slides.
So the goal of our work is to help
presenters make their presentation accessible
And towards this goal, we present Presentation A11y the tools that give
automatic feedback.
to help presenters describe their slides.
Presentation A11y provides Real-Time Feedback, and Post-Presentation Feedback.
The real time feedback interface augments the existing Google Slides
presenter view, to give presenters on what they have
and haven't described. In this video.
the interface highlight slide texts create a colorful circle
brush and an image depicting the circle brush as the speaker
described them.
(The presenter speaking) First, we'll create a colorful circle brush and you'll see
the squiggly line pictured on the right.
With these rainbow circle sort of getting wider and smaller as it goes.
Presenters can also turn on or off the feedback display.
On the other hand, our post-presentation feedback
interface augments the Google Slides editor to let users review
their results.
Users can quickly identify what like they did and did not
describe well by glancing at a slide overview.
It shows poorly described slides in red. When editing each individual
slide, Presentation A11y highlights the element they were described
during the presentation in green
A results panel shows the slide’s coverage percentage,
the transcript records during the talk, and a specific suggestion
for how to make the slide more accessible.
The interface updates the coverage percentage as the presenters edit the slides.
Or edit the transcripts to add the descriptions.
We invited 16 people to present
and review their own slides with Presentation A11y.
Users presented half of the slides with real time feedback and
half without
After presentation, they review their slides with
and without out post-presentation feedback.
Presentation A11y’s real-time feedback
helped people describe significantly more of their text and images than the default interface.
For text, people covered 57% of text with
and 46% of text without our system.
People achieved an image coverage score of 3.5 out of 5 with and 3.1 out of 5 without our system
In addition, the post-presentation feedback help people
identify significantly more accessibility changes to make in the future
than they did without our feedback.
People identified 2.3 changes with our system and 0.7 without.
In the future we plan to provide people more granular feedback on how to describe
their images and diagrams.
Also, our current interface is not accessible for blind and low vision presenters
because it relies on visuals for feedback.
We plan to make a screen reader accessible tool
in the future.
Finally, we plan to deploy the tool as a Google Chrome Extension.
With that, I would like to end my talk.
For more information, you can find it at sayitall.github.io
Thank you.