WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Accessible automated tools

for

From: Angela French
Date: Jun 11, 2019 2:38PM

I tried out FastPass on Outlook Webmail. Lots of failures. Interesting....

-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Michael Ausbun
Sent: Thursday, June 6, 2019 10:14 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Accessible automated tools

I am curious what folks think of the Microsoft/deque partnership with the Microsoft accessibility InSite tool? The user experience seems decent, and it seems to have much of the Axe functionality. Just curious.
Naturally, automated tools are not the exclusive way to test; when automated tools are used though, our team wants to make sure that they are in alignment with industry standards and that our testers (like me) who are native users of access technology can use the tools.
Many thanks for everyone's suggestions! I'm taking notes and cross analyzing against what I previously believed and the literature I have read.
Respectfully,
michael



--
Michael Duane Ausbun, MA
Specialist, Learning Experience,
Universal Design and Accessibility Team
Salt Lake City, Utah
[WGU Learning Experience]

Western Governors University
4001 South 700 East, Suite 700
Salt Lake City, UT 84107
<EMAIL REMOVED>


[Western Governors University]<wgu.edu>



From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Birkir R. Gunnarsson
Sent: Wednesday, June 5, 2019 3:29 PM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Accessible automated tools

[EXTERNAL EMAIL] WARNING: Be wise. Be cautious.

Good recommendation.
Sadly WCAG relegates clear language requirements mostly to AAA (best
practice) success criteria, but clear language benefits everybody.
It's especially important when working in banking, insurance or similar not to get too tangled up in the abbreviations and complex terms and language that people who are professionals hear and use as part of their jobs every day. When they write they sometimes forget that the clients are not financial professionals, not most of them anyway.

Screen readers are highly useful accessibility tools, but they have their drawbacks, like any other tool.
For some complex issues, you sometimes have to analyze whether the problem is with the code or how the screen reader processes the code.
If it's the latter it's important to file an issue with the screen reader vendor, so you can use this code in the future (when it is fixed).
depending on the importance of the content that is being communicated you may want to create a workaround or let the code stand as is.
You have to be aware of the accessibility supported requirements of WCAG (which is why, in addition to testing with automated testing tools and bookmarklets, you should do quick testing with a screen reader, especially on templates and key pages).



On 6/5/19, Amber James < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:
> Hi all,
>
> In addition to the great automated testing tools already mentioned
> (Axe, Wave, bookmarklets), I use the Hemingway Editor
> <http://www.hemingwayapp.com/<;http://www.hemingwayapp.com/>;> to check
> the grade level and complexity of copy on a sentence level. I come to
> accessibility by way of content strategy and copywriting, so I always
> have my eyes on the words. If anyone has questions about that, lmk.
>
> Cheers,
> Amber James
> Accessibility Consultant
> U.S. Bank
> https://www.linkedin.com/in/amberajames/<https://www.linkedin.com/in/a
> mberajames/>
>
>
>
> On Wed, Jun 5, 2019 at 1:00 PM < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:
>
>> Send WebAIM-Forum mailing list submissions to
>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>> http://list.webaim.org/mailman/listinfo/webaim-forum<;http://list.weba
>> im.org/mailman/listinfo/webaim-forum>
>> or, via email, send a message with subject or body 'help' to
>> <EMAIL REMOVED> <mailto:webaim-forum-request@list
>> .webaim.org>
>>
>> You can reach the person managing the list at
>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED>
>> aim.org>
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of WebAIM-Forum digest..."
>> Today's Topics:
>>
>> 1. Re: Accessible automated tools (Birkir R. Gunnarsson) 2. Re: WCAG
>> 2.0 level AA and the combination between screen readers and browsers
>> compatibility (Birkir R. Gunnarsson) 3. Screen readers that DISPLAY
>> what they see (Haim Roman) 4. Re: Screen readers that DISPLAY what
>> they see (Farough, David (CFP/PSC)) 5. Upcoming free webinars on
>> accessibility (Marissa Sapega) 6. Fill in the Blanks Form
>> Implementation (Tiller, Mary)
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Birkir R. Gunnarsson"
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 07:04:11 -0400
>> Subject: Re: [WebAIM] Accessible automated tools For using automated
>> accessibility tols with a screen reader, check out
>> http://www.bats.fyi<;http://www.bats.fyi>;
>>
>> For automated tools, Axe from Deque and Wave from WebAIM are the most
>> widely used tools, both are reliable, I've used both extensively.
>> Axe is open source, used by Google and Microsoft, reliable for
>> automated scans and comes in various forms including browser add-ons
>> and command line.
>> The newly released Arc inspector tool from the Paciello Group looks
>> promising and is picking up some subtle accessibility problems. I
>> have yet to do a deeper dive on it but I am interested in exploring
>> it further.
>> The web accessibility practitioner survey has a table of the most
>> widely used tools:
>> https://webaim.org/projects/practitionersurvey2/<https://webaim.org/p
>> rojects/practitionersurvey2/>
>>
>> For manual inspection we rely on a selection of bookmarklets to
>> visualize information such a screen reader markup.
>> We like ANDI (accessible name and description inspector), not its
>> automated test warnings but its ability to visualize accessible name,
>> description, headings, tables etc.
>> Blind testers can do this with a screen reader but sighted testers
>> need something simple and ANDI is a good fit.
>> We use a handful of other bookmarklets, but it'd get too long to list
>> them.
>> We also roll some of our own and are experimenting with writing
>> custom tests and bookmarklets.
>>
>>
>>
>>
>> On 6/3/19, Steve Green < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:
>> > We used to use Paciello's Accessibility Toolbar a lot, but now I
>> > only
>> use it
>> > for the Images List feature and the colour contrast analyser.
>> > Almost all
>> our
>> > testing is done by inspection of the user interface or by using
>> > browser developer tools to inspect the code. My understanding is
>> > that browser developer tools are pretty much accessible.
>> >
>> > Apart from that, we use a handful of bookmarklets to improve the
>> efficiency
>> > of the testing, although the pass / fail decision is always made by
>> > a person, not the tool. Some of these will be accessible, such as
>> > the one
>> we
>> > use to check the text spacing (SC 1.4.12). Others will be
>> > inaccessible,
>> such
>> > as the one that uses coloured rectangles to show all the landmarks
>> > on a page. The user experience of all these is good, which is not
>> > surprising because they are all single-purpose tools.
>> >
>> > We rarely use automated tools, and it is invariably a painful
>> > experience when we do. Much of the time is spent trying to work out
>> > what the tool is doing and why it is not giving the results we
>> > would expect, even after taking into account what a tool can and
>> > cannot do in principle.
>> >
>> > Steve Green
>> > Managing Director
>> > Test Partners Ltd
>> >
>> >
>> >
>> > -----Original Message-----
>> > From: WebAIM-Forum
>> > < <EMAIL REMOVED> <mailto:webaim-forum-bounces@l
>> > ist.webaim.org>> On Behalf Of Michael Ausbun
>> > Sent: 03 June 2019 17:40
>> > To: WebAIM Discussion List
>> > < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> > Subject: [WebAIM] Accessible automated tools
>> >
>> > Dear List,
>> > Background
>> > My name is Michael Ausbun, and I am a blind accessibility
>> > specialist working for Western Governors University. I have been an
>> > avid user of assistive technology for 18 years, involved with
>> > accessibility evaluation for 9 years, and have taught access
>> > technology off and on for
>> 9
>> > years. I have begun to work on a project here at WGU regarding our
>> > evaluation methodology, including the tools we use for automated
>> testing. We
>> > are well aware of the functional limitations of automated tools and
>> > we
>> are
>> > aware that there are several automated tools out there.
>> > Questions
>> >
>> > 1. What tools are people using for their evaluations (automated or
>> > otherwise?)
>> > 2. How accessible are the tools being used?
>> > 3. How is the user experience when implementing the tools being used?
>> > Thank you for your time and energy! I have read through several
>> > publications-peer reviewed and not peer reviewed. I also read
>> > through several testing methodologies used throughout the industry;
>> > I came out
>> the
>> > other side with more questions than I went in with...mostly around
>> > the
>> why,
>> > but also the what.
>> > Respectfully,
>> > Michael
>> >
>> > --
>> > Michael Duane Ausbun, MA
>> > Specialist, Learning Experience,
>> > Universal Design and Accessibility Team Salt Lake City, Utah [WGU
>> > Learning Experience]
>> >
>> > Western Governors University
>> > 4001 South 700 East, Suite 700
>> > Salt Lake City, UT 84107
>> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>> >
>> >
>> > [Western Governors University]<wgu.edu>
>> >
>> >
>> >
>> > From: WebAIM-Forum
>> > < <EMAIL REMOVED> <mailto:webaim-forum-bounces@l
>> > ist.webaim.org>> On Behalf Of
>> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>> > Sent: Monday, June 3, 2019 8:34 AM
>> > To: 'WebAIM Discussion List'
>> > < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> > Subject: Re: [WebAIM] MathML and simple math content
>> >
>> > [EXTERNAL EMAIL] WARNING: Be wise. Be cautious.
>> >
>> > Isabel H wrote:
>> > "the upshot of which sadly seems to be that there's no tried and
>> > trusted means of presenting mathematical content in a way that
>> > reliably works for screenreader or Braille users."
>> >
>> > That's correct. There is no one single method of creating
>> > accessible math that works seamlessly across all assistive
>> > technologies. Also, no one
>> method
>> > when we create the accessible content and move the math from an
>> > equation editor into documents, websites, EPUBs, whatever.
>> >
>> > It's a real mess for the entire community.
>> >
>> > Someone needs to fix this!
>> >
>> > - - -
>> > Bevi Chagnon, founder/CEO |
>> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> <mailto: <EMAIL REMOVED> %3cmai
>> > lto: <EMAIL REMOVED> >>
>> > - - -
>> > PubCom: Technologists for Accessible Design + Publishing consulting .
>> > training . development . design . sec. 508 services Upcoming
>> > classes at
>> > www.PubCom.com/classes<;http://www.PubCom.com/classes>;<http://www.Pu
>> > bCom.com/classes<http://www.PubCom.com/classes>;>
>> > - - -
>> > Latest blog-newsletter - Accessibility Tips at
>> > www.PubCom.com/blog<;http://www.PubCom.com/blog>;<http://www.PubCom.c
>> > om/blog<http://www.PubCom.com/blog>;>
>> >
>> > -----Original Message-----
>> > From: WebAIM-Forum
>> > < <EMAIL REMOVED> <mailto:
<mailto: <EMAIL REMOVED> %3cmailto:%0b>>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>>
>> > On Behalf Of Isabel Holdsworth
>> > Sent: Monday, June 3, 2019 9:48 AM
>> > To: WebAIM Discussion List
>> > < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> <m
>> > ailto: <EMAIL REMOVED> %3cmailto: <EMAIL REMOVED>
>> > m.org>>>
>> > Subject: Re: [WebAIM] MathML and simple maths content
>> >
>> > Thank you Mallory for such a long and comprehensive reply!
>> >
>> > I've learned a lot from this thread, the upshot of which sadly
>> > seems to
>> be
>> > that there's no tried and trusted means of presenting mathematical
>> content
>> > in a way that reliably works for screenreader or Braille users.
>> >
>> > Ah well, we'll just keep doing what we're doing and use MathML for now.
>> >
>> > Thanks again, Isabel
>> > >> > >> > http://list.webaim.org/<;http://list.webaim.org/>;<http://list.webaim
>> > .org/<http://list.webaim.org/>;> List archives at
>> > http://webaim.org/discussion/archives<;http://webaim.org/discussion/
>> > archives><
>> http://webaim.org/discussion/archives<;http://webaim.org/discussion/ar
>> chives>>
>> > >> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> <ma
>> > ilto: <EMAIL REMOVED> %3cmailto: <EMAIL REMOVED>
>> > .org>>
>> >
>> > >> > >> > http://list.webaim.org/<;http://list.webaim.org/>;<http://list.webaim
>> > .org/<http://list.webaim.org/>;>
>> > List archives at
>> > http://webaim.org/discussion/archives<;http://webaim.org/discussion/
>> > archives><
>> http://webaim.org/discussion/archives<;http://webaim.org/discussion/ar
>> chives>>
>> > >> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> <ma
>> > ilto: <EMAIL REMOVED> %3cmailto: <EMAIL REMOVED>
>> > .org>> >> > >> > http://list.webaim.org/<;http://list.webaim.org/>;
>> > List archives at
>> > http://webaim.org/discussion/archives<;http://webaim.org/discussion/
>> > archives> >> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>> >
>>
>>
>> --
>> Work hard. Have fun. Make history.
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Birkir R. Gunnarsson"
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 07:12:10 -0400
>> Subject: Re: [WebAIM] WCAG 2.0 level AA and the combination between
>> screen readers and browsers compatibility Hi
>>
>> WCAG 2.0 has a section called Core Conformance requirements.
>> One of those requirements is that content must be "accessibility
>> supported".
>> The wording is vague but the way I interpret it is that you should be
>> able to demonstrate that it works with at least one popular
>> combination of a browser and a screen reader (ideally also check for
>> screen magnification and speech recocnition, though that limits your
>> options).
>> I generally recommend to single out NVDA as the screen reader, and
>> either FF or Chrome as a default screen reader testing platform (it
>> used to be FF but I am getting increasingly frustrated with FF these
>> days and Chrome is coming in stronger).
>> NVDA is open source so it can be upgraded as web technologies are
>> updated. You can file NVDA issues through GitHub so if you discover
>> systematic problems you can demonstrate a record of having tried your
>> best to fix them.
>> Jaws is powerful and it is the screen reader I personally use the
>> most, but it's not perfect either and upgrading it is not cheap, so I
>> have not assumed that users can necessarily stay up-to-date with the
>> latest and (hopefully) greatest versions.
>> The differences between the two are not huge.
>> Generally, if it works with one combination, it will work with the
>> other (though beware of IE11 as it is effectively done and no longer
>> keeps up with evolving technologies).
>>
>>
>>
>>
>> On 6/3/19, Eilana Benish < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >> wrote:
>> > Hi all,
>> >
>> > is there any document from the WCAG which specifies how many screen
>> readers
>> > and browser combinations should be compatible to the WCAG 2 level AA?
>> >
>> > from my experience, it is impossible to meet all the combinations
>> > with
>> all
>> > screen readers and browsers when websites implement ARIA and HTML5
>> >
>> > Here in Israel, we must comply to the Israeli 5568 standard which
>> > based
>> on
>> > the WCAG 2.0 Level AA and the modification maid so the 2.4.10
>> > Section Headings level AAA <
>> https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mechanisms-head
>> ings.html<https://www.w3.org/TR/UNDERSTANDING-WCAG20/navigation-mecha
>> nisms-headings.html>
>> >
>> > criteria will be also included in the Israeli 5568 standard (I
>> > insisted
>> for
>> > that downgrade back then …).
>> >
>> > HTML 5 and ARIA are commonly used, many times incorrectly and when
>> > not needed… and then the fixing issues starts.
>> >
>> > I know the common combinations for screen reader and browsers
>> >
>> > · NVDA + FF
>> >
>> > · JAWS + Google chrome and IE
>> >
>> > · IOS + safari
>> >
>> > · Talkback + android
>> >
>> > I`m testing in the latest versions …
>> >
>> > But sometimes the developer develops the sites with JAWS for chrome
>> > and
>> IE
>> > and leaves the rest behind. And then I have to ask to repair… and
>> > then
>> they
>> > start to argue
>> >
>> > And at the end, the client wonts to be sure that his website is
>> > WCAG and the regulations compliant. And in Israel, I am authorized
>> > accessibility consulted – and my signature required
>> >
>> > So, I need to know what the WCAG have to say about the compliant issue.
>> >
>> > I hope someone can help me with that
>> >
>> > Thanks in advance.
>> >
>> > Eilana Benish
>> >
>> >
>> >
>> >
>> >
>> >
>> > *ובכבוד רב, אילנה בניש, *
>> >
>> > *מורשה נגישות שירות (2200)*
>> >
>> > *ליווי וניהול פרויקטים: **נגישות ושמישות אינטרנט וטכנולוגיות מידע*
>> > <
>> https://adn-accesstime.com/2018/10/20/אפליקציית-תזכורות-מתקדמת-remind
>> er-reminders-with-ל-ios/<https://adn-accesstime.com/2018/10/20/אפליקצ
>> יית-תזכורות-מתקדמת-reminder-reminders-with-ל-ios/>
>> >
>> >
>> > *טלפון 050-7100367 דוא"ל
>> > ** <EMAIL REMOVED> *<mailto:** <EMAIL REMOVED> *>
>> > < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> >
>> > *האפליקציה ▐ **IOS*
>> > <
>> https://itunes.apple.com/app/id1438649378?fbclid=IwAR2xQt2j9TXnIBdOVz
>> 1oY3T0oBPTepgWndQIlruALWr4q7T4gTZ1mUJAmCQ<https://itunes.apple.com/ap
>> p/id1438649378?fbclid=IwAR2xQt2j9TXnIBdOVz1oY3T0oBPTepgWndQIlruALWr4q
>> 7T4gTZ1mUJAmCQ>
>> >*
>> > ▐ **אנדרואיד*
>> > <
>> https://play.google.com/store/apps/details?id=com.adn_accesstime.pres
>> spadnews&fbclid=IwAR2KslNcOzRqC8zD_Dpr9qI5EvHFjKAQK2-lCwFoMLVgVHw-M34
>> OZIuUTDo
>> >
>> > >> > >> > http://list.webaim.org/<;http://list.webaim.org/>;
>> > List archives at
>> > http://webaim.org/discussion/archives<;http://webaim.org/discussion/
>> > archives> >> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>> >
>>
>>
>> --
>> Work hard. Have fun. Make history.
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Haim Roman < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 15:03:00 +0300
>> Subject: [WebAIM] Screen readers that DISPLAY what they see Yeah, I
>> know, sounds very redundant.
>> But recently I discovered a bug where aria-label text obscured (to
>> the screen reader) the test of the HTML <LABEL> tag.
>> I really didn't want to use a screen reader because I'm not used to
>> them and my hearing is not as good as my vision (also, someone else
>> was going to test it).
>> But someone told me that there is *software to visually display what
>> a screen reader would "see"*, and in the same order that a screen
>> reader would see it.
>> Does anyone know of such software
>>
>> Thanks
>>
>> >> Howard (Haim) Roman --
>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > -- 052-8-592-599 --
>> חיים רומן
>> LinkedIn:
>> https://www.linkedin.com/in/haimroman<https://www.linkedin.com/in/hai
>> mroman>
>>
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Farough, David (CFP/PSC)"
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 14:04:36 +0000
>> Subject: Re: [WebAIM] Screen readers that DISPLAY what they see Your
>> best option would be the NVDA screen reader. Available at
>> https://www.nvaccess.org/<https://www.nvaccess.org/>
>>
>> From the user manual:
>>
>> 12.2. Speech Viewer
>>
>> For sighted software developers or people demoing NVDA to sighted
>> audiences, a floating window is available that allows you to view all
>> the text that NVDA is currently speaking.
>>
>> To enable the speech viewer, check the "Speech Viewer" menu item
>> under Tools in the NVDA menu. Uncheck the menu item to disable it.
>>
>> The speech viewer window contains a check box labeled "Show speech
>> viewer on startup". If this is checked, the speech viewer will open
>> when NVDA is started. The speech viewer window will always attempt to
>> re-open with the same dimensions and location as when it was closed.
>>
>> While the speech viewer is enabled, it constantly updates to show you
>> the most current text being spoken. However, if you click or focus
>> inside the viewer, NVDA will temporarily stop updating the text, so
>> that you are able to easily select or copy the existing content.
>>
>> To toggle the speech viewer from anywhere, please assign a custom
>> gesture using the Input Gestures dialog.
>>
>> -----Original Message-----
>> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On
>> Behalf Of Haim Roman
>> Sent: Wednesday, June 05, 2019 08:03 AM
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Subject: [WebAIM] Screen readers that DISPLAY what they see
>>
>> Yeah, I know, sounds very redundant.
>> But recently I discovered a bug where aria-label text obscured (to
>> the screen reader) the test of the HTML <LABEL> tag.
>> I really didn't want to use a screen reader because I'm not used to
>> them and my hearing is not as good as my vision (also, someone else
>> was going to test it).
>> But someone told me that there is *software to visually display what
>> a screen reader would "see"*, and in the same order that a screen
>> reader would see it.
>> Does anyone know of such software
>>
>> Thanks
>>
>> >> Howard (Haim) Roman --
>> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> > -- 052-8-592-599 --
>> חיים רומן
>> LinkedIn:
>> https://www.linkedin.com/in/haimroman<https://www.linkedin.com/in/hai
>> mroman> >> >> http://list.webaim.org/<;http://list.webaim.org/>;
>> List archives at
>> http://webaim.org/discussion/archives<;http://webaim.org/discussion/ar
>> chives> >> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: Marissa Sapega
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To: WebAIM Discussion List
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 14:21:47 +0000
>> Subject: [WebAIM] Upcoming free webinars on accessibility Hi folks,
>>
>> I wanted to let you know about a few upcoming webinars given by The
>> Paciello Group:
>>
>> June 6 at 12pm ET: Hiring and Retaining Employees with Disabilities
>>
>> Join TPG's Ryan Jones for this exclusive webinar. Ryan has presented
>> on hiring people with disabilities at several industry conferences
>> and has spent the past five years helping companies ensure
>> accessibility for their employees.
>> This 60-minute webinar will cover the four stages of hiring and retention:
>>
>> 1. Applications and Interviews – Can people with disabilities use
>> your website to apply for jobs?
>> 2. Onboarding – Once someone with a disability has been hired they'll
>> need access to corporate digital tools like an intranet, knowledge
>> base, timesheets, human resource information, and more.
>> 3. Employment – As part of their job, employees will make use of
>> multiple forms of technology.
>> 4. Accessibility Program – Current employees need to be educated
>> about people with disabilities to mitigate misconceptions and biases.
>>
>> Attendance is free, just register online at :
>> https://zoom.us/webinar/register/4415581231937/WN_ItG4SGTISvqhgeMpggG55w<https://zoom.us/webinar/register/4415581231937/WN_ItG4SGTISvqhgeMpggG55w>.
>>
>> June 20 at 12pm ET: Introduction to TPG's Free Accessibility Testing
>> Tool, ARC Toolkit
>>
>> In this webinar, we will walk you through our brand-new Chrome
>> Extension, ARC Toolkit. It's a professional-level testing tool that
>> gives you the power to quickly and efficiently evaluate screens for
>> accessibility and uncover issues related to the WCAG 2.1 Level A and
>> AA guidelines. The Toolkit uses the ARC ruleset, the same rules used
>> by default in TPG's ARC platform for website monitoring and analysis.
>>
>> By extending these automated rules outside of the platform, ARC
>> testing can now be easily integrated into your development and
>> testing environments to be performed at any time. The Toolkit does
>> not require an ARC subscription but the benefits when used in
>> parallel with the platform are substantial. In this webinar we'll
>> show you how to use ARC Toolkit for testing web content.
>>
>> Attendance is free, please register online at :
>> https://zoom.us/webinar/register/6015596580206/WN_euxVglp7TYKiL8l7rzC
>> yng<https://zoom.us/webinar/register/6015596580206/WN_euxVglp7TYKiL8l
>> 7rzCyng>
>>
>> Please let me know if you have any questions.
>>
>> Regards,
>>
>> Marissa Sapega
>> Marketing Manager
>>
>> [The Paciello Group logo]
>> The Paciello Group
>> https://www.paciellogroup.com<https://www.paciellogroup.com><https://
>> www.paciellogroup.com/<;https://www.paciellogroup.com/>>
>>
>> A Vispero Company
>> https://vispero.com/<https://vispero.com/>
>> M: 484.577.9465
>>
>> --
>> This message is intended to be confidential and may be legally privileged.
>> It is intended solely for the addressee. If you are not the intended
>> recipient, please delete this message from your system and notify us
>> immediately. Any disclosure, copying, distribution or action taken or
>> omitted to be taken by an unintended recipient in reliance on this
>> message is prohibited and may be unlawful.
>>
>>
>>
>> ---------- Forwarded message ----------
>> From: "Tiller, Mary"
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> To:
>> " <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >"
>> < <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >>
>> Cc:
>> Bcc:
>> Date: Wed, 5 Jun 2019 15:56:04 +0000
>> Subject: [WebAIM] Fill in the Blanks Form Implementation Good day,
>>
>> Does anyone have a public implemented example of an accessible "fill
>> in the blanks" form that uses natural language. A form that gathers
>> information from a user that requires them to fill in the blanks,
>> example: "My last name is_________"
>>
>> Thank you!
>>
>> >> >> http://list.webaim.org/<;http://list.webaim.org/>;
>> List archives at
>> http://webaim.org/discussion/archives<;http://webaim.org/discussion/ar
>> chives> >> <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>>
> > > http://list.webaim.org/<;http://list.webaim.org/>;
> List archives at
> http://webaim.org/discussion/archives<;http://webaim.org/discussion/arc
> hives> > <EMAIL REMOVED> <mailto: <EMAIL REMOVED> >
>


--
Work hard. Have fun. Make history.