W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 2017

RE: Libraries to build web pages.

From: SALES, TERRY LYNN <TERRYLYNN.SALES@cbp.dhs.gov>
Date: Fri, 6 Jan 2017 14:26:20 +0000
To: Srinivasu Chakravarthula <lists@srinivasu.org>, "Sean Murphy (seanmmur)" <seanmmur@cisco.com>
CC: WAI Interest Group <w3c-wai-ig@w3.org>
Message-ID: <CD6739563257E640956C81ABE78DD091E2B5C151@D2ASEPREA011>
At US Customs, we started a multi-app system with Bootstrap, made 508 compliant components, created a framework, and raised that to the Customs level for all Customs development. Having the base Bootsrap compliant out of the box would be huge!  It would make my job less secure, but there would always be those who customize the compliance out :)

________________________________
From: Srinivasu Chakravarthula
Sent: Friday, January 06, 2017 12:11:07 AM
To: Sean Murphy (seanmmur)
Cc: WAI Interest Group
Subject: Re: Libraries to build web pages.

Absolutely, I see companies are moving towards using libraries and plugins rather than coding from scratch. So I completely agree that these platforms/ frameworks / libraries have to provide accessibility out of the box. Also, these tools should have ability to flag if there are accessibility violations while inserting content.

Best,
Vasu

Regards,

Srinivasu Chakravarthula - Twitter: http://twitter.com/CSrinivasu/
Website: http://www.srinivasu.org | http://serveominclusion.com

Let's create an inclusive web!

Lead Accessibility Consultant, Informatica
Hon. Joint Secretary, The National Association for the Blind, Karnataka Branch

On Fri, Jan 6, 2017 at 9:40 AM, Sean Murphy (seanmmur) <seanmmur@cisco.com<mailto:seanmmur@cisco.com>> wrote:
Team,

>From my point of view, development environments which include the libraries, bootstrap templates, code generators, etc are key focus areas to improve accessibility. Some articles I have reviewed on the net indicate web developers in the future will not need to have the level of development knowledge, but more design and business knowledge. Some of the tools I have used donít include or even discuss accessibility in their environment. Thus the topic I am rasing is slightly left field and I am hoping people can help.

UAAG from my reading is focusing on the browser, media players and plugins. Thus companies who develop libraries for web authors such as rich edit controls, toolbars, drop down (combo boxes), etc should follow the UAAG standards?

Those vendors who create development environments which allow the author to build the web site without using any coding should be following the ATAG standards. If the tool is using libraries as previously described with the vendor develops. Then they should follow the UAAG standards as well?

If I am correct in the above, what is peoples views on the best method of educating, encouraging or even using legal means to get these vendors/developers to start utilising the standards? As the end-user of the web product  only focuses on the organisation that is publishing the web content, not the tools or development environment.

Is any one aware of any company including accessibility in their contracts with vendors who provide the development environment?

AS some of the tools and libraries people use for development is open source. How does legal laws like the ADA or section 508 apply here? As from my understanding open source and like projects are not owned by anyone. Thus getting these groups of people to follow the accessibility standards is nearly impossible. Especially if you are not a coder to assist with the project.

I just see this as a big area of concern which I donít see major improvements. If the development environment which builds the web product was accessible or supported the standards. Then I think a lot of the issues would be addressed.

Sean Murphy
Received on Friday, 6 January 2017 14:27:02 UTC

This archive was generated by hypermail 2.3.1 : Friday, 6 January 2017 14:27:06 UTC