Help,

We are in a lawsuit saying our website is not ADA accessible and we must fix these problems ASAP.

I am having trouble knowing what this is or how to fix it.

All onclick handlers should have an equivalent onkeyup or onkeydown handler.
Some users are unable to use a mouse, so use the keyboard instead. Add an equivalent keyboard event handler to help these users.
Line 441 WCAG 2.1 A F54 Section 508 (2017) A F54
<div id="opaquediv" class="ectopaque" style="display:none" onclick="if(event.target==this)this.style.display='none'">

Seems functions.asp line 617 is where this code is getting flagged. Do I need to add something here like onkeypress="this.value=this.value + 'onkeypress '

I don't have any clue I'm just guessing from looking at results from some google searches on this

Scott

Hi Scott

quote:

---

All onclick handlers should have an equivalent onkeyup or onkeydown handler.

---

From what is stated here I would add an "onkeyup" event. For instance...
<div id="opaquediv" class="ectopaque" style="display:none" onkeyup="if(event.target==this)this.style.display='none'" onclick="if(event.target==this)this.style.display='none'">

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

Vince,

Since that is an inc file, this is something the next update would wipe out.

Is that something you could add to your master files so future updates have that taken care of?

I will be sending you other issues as I work on them is they pertain to the master inc files you send updaters out for as lawsuits in the USA will need these to help keep this compliant for other users.

Scott

Scott

Ok, I added the onkeyup command to incfunctions.asp and now I am still getting the following

<div id="opaquediv" class="ectopaque" style="display:none" onkeyup="if(event.target==this)this.style='none'" onclick="if(event.target==this)this.style.display='none'">


onkey handlers on static elements like div and span cannot be triggered unless tabindex is set.
onkey handlers cannot be activated from the keyboard unless the user can tab to the element. By default only links and form controls can be tabbed to. Set tabindex=0 on the static element to allow the user to tab to it.
Impact on users:

JAWS Tabbing: Users cannot tab to the control to activate the onkey handler.
NVDA Tabbing: Users cannot tab to the control to activate the onkey handler.
VoiceOver Tabbing: Users cannot tab to the control to activate the onkey handler.
Keyboard Tabbing: Users cannot tab to the control to activate the onkey handler.
Line 562 WCAG 2.1 A 2.1.1 Section 508 (2017) A 2.1.1


Scott

Hi Scott
I would be really happy to make changes to the core code for ADA compliance. But what are you using to asses these issues? Is there an official "ADA" testing page?

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

I am down to just 4 major issues on my index page as is. www.beanbag.com

I just can't get by these 4 things
Using Power Mapper to find issues as that is what the layer used see https://try.powermapper.com/Demo/SortSite

Level A
2 issues

Critical Clickable controls should be keyboard accessible. WCAG 2.1 A F15 Section 508 (2017) A F15 1 pages
Add tabindex=0 to allow keyboard users to tab to the control.
https://www.beanbag.com/ Line 800 803 806 809 slide show error can't see as line # do not match up

Critical Clickable controls should have an ARIA role. WCAG 2.1 A F54 Section 508 (2017) A F54 1 pages
Controls that respond to clicks should be given an ARIA role such as role=button or role=link.
https://www.beanbag.com/ Line 800 803 806 809


Scott

This seemed to fix the error message I was getting from PowerMapper.com test.

Is this something you might include on your master files, so it does not get whipped out next update?

Scott

Ok, Tested with NVIDA screen reader. Super close, but ran into a few issues

Detail list is perfect, works great with reader. However, when you fixed that, we lost the product img info

Img now saying "CART" ...Associability now says "Cart" for the product img on both the products.asp page and on cart.asp

also

Thanks.asp page, the role="main" is too low on page. Screen read jumps to bottom of your invoice or thanks. It could be moved up to <Div class="orderreciept" role="main" and then main content would be the thank you my Johnes for your order to my store. etc. Right now, it jumps main content to footer of invoice.

question... any idea on how main content could be updated on cart page... meaning you enter cart, click checkout to go to entering billing, but main content starts back at all your navigation... you have to tab thru everything to get to enter name, then you enter billing and tab checkout for shipping, and again it starts at navigation links, and you have to tab all the way thru back to the place you need to fill out for shipping. I do not know if there is a way to help or change this but would be very helpful to a screen reader to hit checkout and be focused next field to fill out instead of start at first navigation link when the screen changed from 1 to 3 in cart check out process.


Scott

quote:

---

Img now saying "CART" ...Associability now says "Cart" for the product img on both the products.asp page and on cart.asp

---

The HTML that I get for the product image on the products.asp page is this...
<img id="prodimage0" class="prodimage allprodimages" src="prodimages/tpurples.jpg" alt="Purple Large Bean Bag">
Shouldn't the reader get the information from the "alt" ?

Vince



Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater

I'm still getting flagged for onkey items

onkey handlers on static elements like div and span cannot be triggered unless tabindex is set.

error on products.asp page and
on proddetails.asp


<div class="ectopaque" id="opaquediv" style="display: none;" onkeyup="if(event.target==this)this.style.display='none'" onclick="if(event.target==this)this.style.display='none'"></div>

Scott

More details about that error

onkey handlers on static elements like div and span cannot be triggered unless tabindex is set. WCAG 2.1 A 2.1.1 Section 508 (2017) A 2.1.1 2 pages
onkey handlers cannot be activated from the keyboard unless the user can tab to the element. By default only links and form controls can be tabbed to. Set tabindex=0 on the static element to allow the user to tab to it.
Impact on users:

JAWS Tabbing: Users cannot tab to the control to activate the onkey handler.
NVDA Tabbing: Users cannot tab to the control to activate the onkey handler.
VoiceOver Tabbing: Users cannot tab to the control to activate the onkey handler.
Keyboard Tabbing: Users cannot tab to the control to activate the onkey handler.

Scott

Hi Scott
I see the point about the tabindex=0 as that means the background "div" can be tabbed to which makes it possible to fire the keyboard event. I've made the changes now to add that tabindex and the changes are in the updater. But trying this out with an "onkeyup" event means that just tabbing to the background DIV will close it, as releasing the TAB key is an onkeyup event. So the question then is, is there a default for closing? Should it only respond to an Enter keypress for instance? If so, is there a way to give that information to a person using a screen reader? (Such as using an ARIA label for instance such as "Press Enter to Close".)

Vince

Click Here for Shopping Cart Software
Click Here to sign up for our newsletter
Click Here for the latest updater