SitePoint Sponsor

User Tag List

Results 1 to 10 of 10

Thread: WAI compliant?

  1. #1
    SitePoint Wizard silver trophy TheOriginalH's Avatar
    Join Date
    Aug 2000
    Location
    Thailand
    Posts
    4,810
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    WAI compliant?

    http://dev.northants-chamber.co.uk/register2.html

    Have been working on for far too long!

    Is designed to replace the vB sign up screen we currently use. Am just about ready to cut it up and splice it into a prepared .php script (which does everything including the washing up), but want to make sure that my claims and assumptions are correct.

    Have thrown it through Bobby and compared against WAI levels 1 && 2 (wasn't sure about 3) - and I think it's pretty close to up to the mark.

    Anything glaringly obvious that I've missed?
    ~The Artist Latterly Known as Crazy Hamster~
    922ee590a26bd62eb9b33cf2877a00df
    Currently delving into Django, GIT & CentOS

  2. #2
    gingham dress, army boots... silver trophy redux's Avatar
    Join Date
    Apr 2002
    Location
    Salford / Manchester / UK
    Posts
    4,838
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    looks good. i ran it through jaws and the results were quite satisfactory (the only part where it seemed to stutter and choke was around the label for the privacy statement checkbox, for some reason...maybe you could remove the title of that link, as it's exactly the same as the actual link text).
    i would also add an accesskey of ALT+S to submit the whole form, but that's the icing on the cake.
    i only had a cursory glance, so not sure if i've missed something obvious either...
    re·dux (adj.): brought back; returned. used postpositively
    [latin : re-, re- + dux, leader; see duke.]
    WaSP Accessibility Task Force Member
    splintered.co.uk | photographia.co.uk | redux.deviantart.com

  3. #3
    SitePoint Wizard silver trophy TheOriginalH's Avatar
    Join Date
    Aug 2000
    Location
    Thailand
    Posts
    4,810
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Nice stuff, cheers Redux.

    It appears that an access key can only be added to an "a" or "button" element, but not "submit". Would that be accurate? Do you know if I can just add:
    accesskey="S"
    to the submit input tag?
    ~The Artist Latterly Known as Crazy Hamster~
    922ee590a26bd62eb9b33cf2877a00df
    Currently delving into Django, GIT & CentOS

  4. #4
    ☆★☆★ silver trophy vgarcia's Avatar
    Join Date
    Jan 2002
    Location
    in transition
    Posts
    21,235
    Mentioned
    1 Post(s)
    Tagged
    1 Thread(s)
    Accesskey should work with any INPUT element.

  5. #5
    SitePoint Wizard silver trophy TheOriginalH's Avatar
    Join Date
    Aug 2000
    Location
    Thailand
    Posts
    4,810
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Yep, I wasn't reading the guidelines very well there - thanks Vinnie
    ~The Artist Latterly Known as Crazy Hamster~
    922ee590a26bd62eb9b33cf2877a00df
    Currently delving into Django, GIT & CentOS

  6. #6
    gingham dress, army boots... silver trophy redux's Avatar
    Join Date
    Apr 2002
    Location
    Salford / Manchester / UK
    Posts
    4,838
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    accesskey can be added to any element that gets focus. that includes inputs, legends, labels, etc
    just look through the DTD's for elements that have %focus; in their attribute list... http://www.w3.org/TR/xhtml1/#dtds
    re·dux (adj.): brought back; returned. used postpositively
    [latin : re-, re- + dux, leader; see duke.]
    WaSP Accessibility Task Force Member
    splintered.co.uk | photographia.co.uk | redux.deviantart.com

  7. #7
    SitePoint Enthusiast lhatkins's Avatar
    Join Date
    Dec 2002
    Location
    Exeter, UK
    Posts
    52
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    The only thing I would say is that you have fixed your font size so the user can not increase the font via the browser thus making it easier if they have impaired vision, why not change to % or em's?

    Just my 2p's worth.
    Regards

    ---
    Lee

  8. #8
    SitePoint Wizard silver trophy TheOriginalH's Avatar
    Join Date
    Aug 2000
    Location
    Thailand
    Posts
    4,810
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)
    Quote Originally Posted by lhatkins
    The only thing I would say is that you have fixed your font size so the user can not increase the font via the browser thus making it easier if they have impaired vision, why not change to % or em's?

    Just my 2p's worth.
    A very good point. And a bad oversight for partially sighted viewers.

    Not a problem in Opera or Mozilla, but possibly in IE. Any advice on this front guys & gals - what would your preferred method of the two be?
    ~The Artist Latterly Known as Crazy Hamster~
    922ee590a26bd62eb9b33cf2877a00df
    Currently delving into Django, GIT & CentOS

  9. #9
    SitePoint Wizard
    Join Date
    Aug 2002
    Location
    N.Ireland
    Posts
    1,046
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    I tend to use x-small tho it only works with this kinda doctype

    <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">

  10. #10
    SitePoint Enthusiast lhatkins's Avatar
    Join Date
    Dec 2002
    Location
    Exeter, UK
    Posts
    52
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)
    Why not just amend your style sheet Font-size to 80% or whatever you want, then users can over ride this if they need to.
    Regards

    ---
    Lee


Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •