WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: guidelines for accessible HTML and CSS - these ok?

for

From: Ryan E. Benson
Date: Aug 23, 2011 8:54PM


Sandy.

I will take Vincent's comment a smidge further and say that skip links
should go immediately after the <body> tag versus "first item", as
they may read it as going before a DOCTYPE declaration. Since there is
a slew of ways to make skip navs, maybe linking to one you like or
making an example would help too.

--
Ryan E. Benson



On Tue, Aug 23, 2011 at 6:33 PM, Vincent Young < <EMAIL REMOVED> > wrote:
> One change could be:
>
> Was:
> The first item on every page is a *skip to content* link. This link takes
> you to an anchor set at the very top of the content — probably just above
> the <h1>
>
> Could be:
> The first item on every page has a *skip to main content* in-page link. This
> link takes you to an anchor set at the very top of the main content —
> probably just above the <h1>
>
> There seems to be some things missing.  What level of compliance are you
> looking to achieve?  If we are speaking strictly 508 you would surely want
> to include requirements for FRAMES and any other missing paragraph.  If you
> are looking for WCAG compliance you would need to include requirements for
> document language and a host of others.
>
> You give a requirement for adding a label:
> Forms need labels <label for="name">Name:</label> <input id="name"
> type="text" name="textfield" />
>
> but you might want to point the developer to other label examples that make
> use of the TITLE attribute and/or FIELDSET.
>
> You've got a good start.  Hope this helps.
>
>
>
>
>
> On Tue, Aug 23, 2011 at 12:01 PM, Sandy < <EMAIL REMOVED> > wrote:
>
>> hey all,
>>
>> I am getting ready to work with someone who is a very capable coder but
>> not at all knowledgeable about accessibility. I have written some
>> guidelines for the HTML and CSS and I hope you can find a little time to
>> look them over and let me know what I've left out.
>>
>> http://sandyfeldman.com/resources/guidelines/
>>
>> thanks very much,
>> Sandy
>>