E-mail List Archives
Thread: Accessibility of Salesforce
Number of posts in this thread: 7 (In chronological order)
From: Howard Kramer
Date: Thu, Feb 26 2015 7:47AM
Subject: Accessibility of Salesforce
No previous message | Next message →
Hello All,
Has anyone had experience working with the Salesforce platform and
complementary tools such as Visualforce, Squid, etc.? I'm trying to find
out how intrinsically accessible it is and what, if any, types of
accessibility tools, checks, etc., it has?
Thanks,
Howard
--
Howard Kramer
CO-PI - UDUC
*Promoting the Integration of Universal Design into University Curricula*
(UDUC)
Lecturer, Cont. Ed - Evening & Cred Admin
303-492-8672
cell: 720-351-8668
From: Karl Groves
Date: Thu, Feb 26 2015 8:41AM
Subject: Re: Accessibility of Salesforce
← Previous message | Next message →
Howard,
I'd recommend taking a look at Salesforce's VPAT documents:
http://www.salesforce.com/company/legal/508_accessibility.jsp
On a personal level, I use Salesforce and Desk.com for Tenon.
Salesforce itself is an incredibly complicated system. I have no data
to support this but I imagine that the system's complexity may
exacerbate any accessibility issues the system has.
It appears that newer Salesforce products have better accessibility
than stuff built on legacy code. Desk.com, for instance, is pretty
good. That doesn't mean it is perfect, which is why Tenon also accepts
support requests via email and telephone. Just the other day though I
engaged in a chat over Desk.com with a user on NVDA.
On Thu, Feb 26, 2015 at 9:47 AM, Howard Kramer < = EMAIL ADDRESS REMOVED = > wrote:
> Hello All,
>
> Has anyone had experience working with the Salesforce platform and
> complementary tools such as Visualforce, Squid, etc.? I'm trying to find
> out how intrinsically accessible it is and what, if any, types of
> accessibility tools, checks, etc., it has?
>
> Thanks,
> Howard
>
>
> --
> Howard Kramer
> CO-PI - UDUC
> *Promoting the Integration of Universal Design into University Curricula*
> (UDUC)
> Lecturer, Cont. Ed - Evening & Cred Admin
> 303-492-8672
> cell: 720-351-8668
> > > --
Karl Groves
www.karlgroves.com
@karlgroves
http://www.linkedin.com/in/karlgroves
Phone: +1 410.541.6829
Modern Web Toolsets and Accessibility
https://www.youtube.com/watch?v=_uq6Db47-Ks
www.tenon.io
From: Howard Kramer
Date: Thu, Feb 26 2015 11:40AM
Subject: Re: Accessibility of Salesforce
← Previous message | Next message →
Hi Karl,
Thanks for that feedback. And I'll take a look at the VPAT.
-Howard
On Thu, Feb 26, 2015 at 8:41 AM, Karl Groves < = EMAIL ADDRESS REMOVED = > wrote:
> Howard,
>
> I'd recommend taking a look at Salesforce's VPAT documents:
> http://www.salesforce.com/company/legal/508_accessibility.jsp
>
> On a personal level, I use Salesforce and Desk.com for Tenon.
> Salesforce itself is an incredibly complicated system. I have no data
> to support this but I imagine that the system's complexity may
> exacerbate any accessibility issues the system has.
>
> It appears that newer Salesforce products have better accessibility
> than stuff built on legacy code. Desk.com, for instance, is pretty
> good. That doesn't mean it is perfect, which is why Tenon also accepts
> support requests via email and telephone. Just the other day though I
> engaged in a chat over Desk.com with a user on NVDA.
>
> On Thu, Feb 26, 2015 at 9:47 AM, Howard Kramer < = EMAIL ADDRESS REMOVED = >
> wrote:
> > Hello All,
> >
> > Has anyone had experience working with the Salesforce platform and
> > complementary tools such as Visualforce, Squid, etc.? I'm trying to find
> > out how intrinsically accessible it is and what, if any, types of
> > accessibility tools, checks, etc., it has?
> >
> > Thanks,
> > Howard
> >
> >
> > --
> > Howard Kramer
> > CO-PI - UDUC
> > *Promoting the Integration of Universal Design into University Curricula*
> > (UDUC)
> > Lecturer, Cont. Ed - Evening & Cred Admin
> > 303-492-8672
> > cell: 720-351-8668
> > > > > > >
>
>
> --
>
> Karl Groves
> www.karlgroves.com
> @karlgroves
> http://www.linkedin.com/in/karlgroves
> Phone: +1 410.541.6829
>
> Modern Web Toolsets and Accessibility
> https://www.youtube.com/watch?v=_uq6Db47-Ks
>
> www.tenon.io
> > > >
--
Howard Kramer
Conference Coordinator
Accessing Higher Ground
303-492-8672
cell: 720-351-8668
AHEAD Association of Higher Education and Disability
From: Caid, Lisa M.
Date: Thu, Feb 26 2015 4:06PM
Subject: Re: Accessibility of Salesforce
← Previous message | Next message →
Hello Howard,
I have not worked with the Salesforce platform, but I've worked in a limited way with the Salesforce.com Lead Accessibility Specialist Jesse H to help us obtain a VPAT, and an updated VPAT for our use of Salesforce. Jesse was very helpful and knowledgeable. I think Jesse is a member of this list.
See Jesse's recent LinkedIn discussion on "Sticky Column in a data table" https://www.linkedin.com/groups/Sticky-Column-in-data-table-4512178.S.5934063171689013250?view=&item=5934063171689013250&type=member&gid=4512178&trk=eml-b2_anet_digest-group_discussions-13-grouppost-name-1&midToken=AQFhlbY-7QiJ9Q&fromEmail=fromEmail&ut=0hiZ_S2-D5p6E1.
And Salesforce UX developed a new color contrast tool for accessibility compliance, ColorSafe, http://colorsafe.co/. More about ColorSafe, Accessible Interface Design, https://medium.com/salesforce-ux/accessible-interface-design-d80e95cbb2c1. ColorSafe is useful to our staff for WCAG 2.0 Success Criteria (SC) 1.4.1, and 1.4.3 testing.
This level of commitment speaks well of Salesforce's accessibility culture, to me.
Sincerely,
Lisa Caid
Accessibility Coordinator
Information Technology - Accessibility
= EMAIL ADDRESS REMOVED =
(806) 651-1241
IT Service Center (806) 651-4357
If you need email content or attachments in alternate formats for accessibility, please send your contact information and the specifics of your request to = EMAIL ADDRESS REMOVED = .
From: Jonathan Avila
Date: Fri, Feb 27 2015 8:10AM
Subject: Re: Accessibility of Salesforce
← Previous message | Next message →
> And Salesforce UX developed a new color contrast tool for accessibility compliance, ColorSafe, http://colorsafe.co/. More
Unfortunately the colors used on the main page (white on a green) do not meet the WCAG contrast requirements for sufficient contrast.
Also, the page lacks a vertical scrollbar and content runs off the bottom of the screen. For people who use lower resolution or who use browser zoom scrollbars should not be prevented from being displayed. The wheel on the mouse can't even be used to scroll.
Jonathan
--
From: Jesse Hausler
Date: Fri, Feb 27 2015 11:59AM
Subject: Re: Accessibility of Salesforce
← Previous message | Next message →
Hey Folks,
I'm very glad to see a discussion about Salesforce here on Webaim. Howard,
I can try to answer your question.
As you mentioned, there are numerous ways to build on our platform. Our
Visualforce components in the <apex:> namespace largely support
accessibility. They have built in techniques for labeling form fields,
using fieldsets, adding image alts, and other basics. When it comes to more
complex UI, it may be safer from an accessibility standpoint to build or
use a 3rd party JS library that you approve of. Visualforce components were
built very long ago before modern standards and ARIA, etc. We recommend
that developers test their custom UI on our platform as they would any
other UI that they build, meaning we don't offer any specific accessibility
testing tools for VF.
We now offer a new technology for building on our platform called Lightning
Components. These were built from scratch to be accessible following the
w3c's specifications for semantics, keyboard behavior, and ARIA. You can
check out the open source sibling to Lightning Components, named Aura, on
github: https://github.com/forcedotcom/aura. These components do come
packaged with JS accessibility tests.
As Lisa and Karl noted, we are making huge strides with the new products
that we are building. We are active in groups like Accessible Innovators
because we want feedback from the community on how we should build more
complex UIs. We are also aiming to help the web community in general by
releasing tools like http://colorsafe.co to the public.
I'd prefer this thread not turn into a discussion about any accessibility
bugs found in that tool, but if you do have things you would like to
report, please contact the developer
<https://github.com/donnieberg/accessible-color-palette/issues>.
If anyone wants to chat about Salesforce in person, I'll be at CSUN next
week where I'll be speaking on how to be successful with Accessibility in
an Agile World
<http://www.csun.edu/cod/conference/2015/sessions/index.php/public/presentations/view/190>;.
I'll also be at Accessibility Web Camp Bay Area this Saturday.
Take care,
Jesse
On Fri, Feb 27, 2015 at 7:10 AM, Jonathan Avila < = EMAIL ADDRESS REMOVED = >
wrote:
> > And Salesforce UX developed a new color contrast tool for accessibility
> compliance, ColorSafe, http://colorsafe.co/. More
>
> Unfortunately the colors used on the main page (white on a green) do not
> meet the WCAG contrast requirements for sufficient contrast.
>
> Also, the page lacks a vertical scrollbar and content runs off the bottom
> of the screen. For people who use lower resolution or who use browser zoom
> scrollbars should not be prevented from being displayed. The wheel on the
> mouse can't even be used to scroll.
>
> Jonathan
>
> --
>
>
From: Jonathan Avila
Date: Sat, Feb 28 2015 8:11PM
Subject: Re: Accessibility of Salesforce
← Previous message | No next message
On Friday I responded to a message about a color safe tool that had been created by the folks at Salesforce. I received numerous off-list messages about my message.
I wanted to apologize that indeed the fonts on the home page of the site provide sufficient contrast when the size and boldness of the text as used on a desktop is taken into consideration. I had personally found this as an issue for me given the contrast level -- but indeed it does meet the minimum requirement. There are other minor items of discussion that I will not raise here though.
I also wanted to apologize that I didn't thank the team for putting this together and sharing this with the community. I am always appreciative of tools that help designers and developers create more accessible content. I failed to express my appreciation in my message and that is something I should have done.
I however will not apologize for bringing some of the accessibility issues up. As a person with disability, some of the issues impacted my use of the page. I was told in an email that the community shouldn't bring bugs or issues up because people have worked hard on these things and that it was harmful to do so. While I agree that if the message is wrong it can be harmful -- there should not be any shame in a person with a disability raising legitimate accessibility issues with a site he/she has accessibility issue with. I guess it's just in my DNA that I have to say something. For example, I just reported a number of accessibility bugs to Apple last night. I'm sure there will be some people on the list who say I should just be happy or thankful with the level of accessibility that Apple has given me as a person with a visual impairment. But I believe that reporting issues and even reporting issues publically is an important step to bring awareness and foster a discussion of accessibility.
Best Regards,
Jonathan
--
Jonathan Avila
Chief Accessibility Officer
SSB BART Group
= EMAIL ADDRESS REMOVED =
703-637-8957 (o)
Follow us: Facebook | Twitter | LinkedIn | Blog | Newsletter