E-mail List Archives
Re: Displaying Content based on previous selection
From: Tyllick,Cliff S (HHSC/DADS)
Date: Sep 28, 2016 9:39AM
- Next message: Alan Zaitchik: "Lectora"
- Previous message: Tim Harshbarger: "Re: Displaying Content based on previous selection"
- Next message in Thread: None
- Previous message in Thread: Tim Harshbarger: "Re: Displaying Content based on previous selection"
- View all messages in this Thread
In my current position I have taken on the role of interpreter of the standards, guidelines, and success criteria for our project teams. Project by project, I'm developing a set of statements that put the solutions in the context of the design they're working on. And they understand that, to the extent I define specific solutions, they are free to propose others for us to discuss. They especially understand that they're free to innovate, so long as their proposed solution is at least as accessible as the standard.
It has dramatically improved their appreciation of the need for accessibility and made them eager to show that they can achieve it.
And because we are focused on the details of a specific project, they don't have to read about stuff their design doesn't have or they can't control. For example, I don't even mention ASCII text, nor do I mention features set by a template they can't change. If, for example, the page template omits the language specification or leaves the title element unpopulated, I file a defect with the keepers of the template and let the current project team know that I have done so.
I call it "teamwork."
Cliff
Cliff Tyllick
Accessibility Coordinator
Civil Rights Office
Texas Health and Human Services Commission
<EMAIL REMOVED>
512-438-2494
From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Tim Harshbarger < <EMAIL REMOVED> >
Sent: Wednesday, September 28, 2016 7:54:10 AM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Displaying Content based on previous selection
If you are having problems making the point to the UX team, one potential way of addressing the problem might be to have a discussion with the UX team regarding what these success criteria mean--with the idea of trying to agree to a common understanding of what the success criteria mean. If you all can agree on a common understanding of these success criteria, then they are more likely to spot these problems sooner and it will also be easier for you to make your case to them when you see problems like this.
I will say that one of the hazards of reaching a common understanding of a success criteria through discussion with people who may not be knowledgeable about accessibility is that the common understanding won't be your understanding. But even so, it means less of a battle to convince them something needs to be addressed--and over time as their understanding becomes better, you can always have the discussion again later to see if it is time for a new common understanding.
Thanks,
Tim
- Next message: Alan Zaitchik: "Lectora"
- Previous message: Tim Harshbarger: "Re: Displaying Content based on previous selection"
- Next message in Thread: None
- Previous message in Thread: Tim Harshbarger: "Re: Displaying Content based on previous selection"
- View all messages in this Thread