![Adrian Cooke](/img/default-banner.jpg)
- 11
- 2 765
Adrian Cooke
Приєднався 31 жов 2019
Creating accessible forms in MS Word (PC version)
How to configure Word for creating accessible, structured documents, and adding fields that can be navigated by screen readers. Topics covered:
00:15 - Configuring Word with a Custom Tab
02:48 - Adding/editing document Title
05:08 - Heading structure
07:20 - Changing default Styles
09:16 - Adding fields
10:16 - Field properties and labels
13:58 - Testing the form
20:30 - Create a custom Style
22:36 - Keyboard navigation
00:15 - Configuring Word with a Custom Tab
02:48 - Adding/editing document Title
05:08 - Heading structure
07:20 - Changing default Styles
09:16 - Adding fields
10:16 - Field properties and labels
13:58 - Testing the form
20:30 - Create a custom Style
22:36 - Keyboard navigation
Переглядів: 1 572
Відео
MathJAX test using VoiceOver in Safari and Firefox
Переглядів 974 роки тому
Testing screen reading of MathJAX equations in VoiceOver using Safari and Firefox.
MathJAX test using NVDA in Firefox
Переглядів 1204 роки тому
Testing how MathJAX equations are voiced in NVDA.
Making digital content accessible for deaf and blind users
Переглядів 3954 роки тому
A presentation called “Text, Accessibility, and You” for the third annual Disability Awareness Month at Gettysburg College. Introduction by Dr. Jeanne Arnold, Chief Diversity Officer. Chapters 00:00 Introduction 01:15 Overview 02:47 Live auto-captioning demo 05:12 What is assistive technology? 09:18 Magnification 09:54 Color 10:55 Screen reader 11:13 Captions 12:05 Reading a meeting (live capti...
Using the Headings menu with VoiceOver in Safari
Переглядів 544 роки тому
Using the Headings menu with VoiceOver in Safari
Screen reading three different PDFs
Переглядів 674 роки тому
An example of text available the screen reader for three different PDFs: an untagged image with no content (text-as-image is unavailable to the screen reader), an untagged document with content (readable, but order is incorrect and alt tags are missing), and the same document after it has been correctly tagged (which fixes reading order and adds alt text).
Automated live transcription of Zoom audio
Переглядів 144 роки тому
Automated live transcription of Zoom audio
Screen reader demonstrating accessible content
Переглядів 274 роки тому
Screen reader demonstrating accessible content
Screen reader demonstrating inaccessible content
Переглядів 2384 роки тому
Screen reader demonstrating inaccessible content
Test of the YouTube Premiere feature
Переглядів 114 роки тому
A test to help us plan our UA-cam Premiere for this weekend.
Creating structured documents in Word
Переглядів 1704 роки тому
A quick overview of configuring Word for Mac to enable accessible web content creation.
Hello Adrian. Thank you for this video. Do I need to download Exported Office UI file to make a document accessible?
This is great. Thanks for capturing this video.
0:59 and then import a file customization 1:02 file in exported ui 1:05 this is called word accessibility 1:06 customizations this is a file you created or is it a file that others can use? if it can't be shared, can you point me to a video or website that will illustrate how I can create such a file? it would be a useful template. thanks.
Did you receive an answer to this? I also would like to know where to find this file.
I am using a mac. Where can I find that downloaded file for the accessibility tab?
So, I have found that when I restrict editing on a form such as this to only filling in fields. NVDA (the screen reader, I don't have access to JAWS) will only read those fields/check boxes etc. and not it won't read any of the text (instructions, etc.). How can we restrict editing and still have the screen reader read the instructions? Thanks in advance!
Hi Ashley, thanks for this question-I need to test this and report back.
Hey, not sure if this helps but I was having a similar issue. Check this video out, ua-cam.com/video/FM_yuCGx7JE/v-deo.html you can make some sections an exception to protection which may be the solution. According to this forum --> accessible-digital-documents.com/blog/you-cant-make-microsoft-word-forms-accessible-enough/, there aren't many workarounds and things just aren't where they need to be with accessibility yet. Hope it helps.
Update: We cannot make exceptions for fillable forms, BUT we can exclude sections as seen here. ua-cam.com/video/Xsh6Tk6xJB8/v-deo.html Finnicky stuff. Best of luck.
This is a helpful video, but I have a few questions about it: 2:27: Why do you use "Heading 1" instead of "Title" to style the title? This is Word, not HTML. 3:52: Once you've set the document's title in the metadata, is there a reason why you don't use it as a field in the document itself (especially for the text styled as Title)? 12:32: Why is it necessary to repeat the Status Bar text in the Help Key text? Doesn't this lead to needless duplication (screen readers reading the same text twice)? 12:55: You change the Status Bar text to "Your first name" whereas the visual label says "First name". For screen reader users with some residual vision, won't a closer match between those strings preferable? 13:35: If students are expected to provide their college email address, why hide this in the status bar info and not make this explicit in the visible label?
Hi Christophe, thanks for your comments. I think either is fine for the heading/title. We are often using Word to prepare content that will end up as HTML. You second suggestion is interesting but not something we have a need for. We are trying to keep the steps as simple as possible for contributors. I need to test your question about the status bar text. I don’t think minor variations in the labels and hint text are likely to be a problem, but am open to feedback on that from screen reader users. I’m not sure what you mean by your last question-this is just an example form, so the labels are not too literal.
Cool countdown feature!