Showing results for 
Search instead for 
Did you mean: 

Updated Accept Hosted form fails WCAG 2.1 AA Compliance

Hello Community,


We use the Accept Hosted payment form within an iFrame to process our payments. A recent update to the form's layout has now caused our checkout process to fail WCAG 2.1 AA compliancy. This is due to the 62.5px of left margin that has been added to the form (why?) which causes our iframe to add a horizontal scrollbar. The rule I am referring to is:


1.4.10 Reflow (AA)

Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
- Vertical scrolling content at a width equivalent to 320 CSS pixels ;
- Horizontal scrolling content at a height equivalent to 256 CSS pixels ;
Except for parts of the content which require two-dimensional layout for usage or meaning.


Unfortunately, PCI SAQ A 3.2 Compliance does not allow JS or CSS to interact with the payment form. Without being able to interact with the form, how can we remove this newly added margin? Dropping to SAQ A-EP is not an option.


Thank you kindly,



Hello @NickL


I found your support case and escalated to support specialist who will look into your issue.



Administrator Administrator

It would great if you can give us some screen shots of the application where you are having this horizontal scroll issue!

Authorize.Net Developer Authorize.Net Developer
Authorize.Net Developer

No problem! Attached are a couple of screenshots uploaded to ImgBB:


Application 1 Accept Hosted iframe has a width of 588px:


Application 2 Accept Hosted iframe has a width of 668px: