WCAG guidance regarding secured/hosted fields for PCI (Payment Card Industry) Compliance
up vote
1
down vote
favorite
I'm looking for some additional WCAG guidance regarding secure fields needed for PCI (Payment Card Industry) compliance for ecommerce. Payment providers now offer a solution for a higher level of conformance where each payment field (credit card number, CVV, and expiration date) is a DOM-injected iframe, comprising of a label, input, error validation, styling, and focus management. These iframed fields are referred as "secure fields".
We are working with our payment provider to improve their markup, however, if they followed all form and iframe related guidelines, would there be any other concerns regarding accessibility?
Thanks!
accessibility pci-compliance wcag wcag2.0
edited Nov 19 at 18:55
prl
4,1431315
asked Nov 19 at 16:16
Beth
286
add a comment |
up vote
1
down vote
favorite
I'm looking for some additional WCAG guidance regarding secure fields needed for PCI (Payment Card Industry) compliance for ecommerce. Payment providers now offer a solution for a higher level of conformance where each payment field (credit card number, CVV, and expiration date) is a DOM-injected iframe, comprising of a label, input, error validation, styling, and focus management. These iframed fields are referred as "secure fields".
We are working with our payment provider to improve their markup, however, if they followed all form and iframe related guidelines, would there be any other concerns regarding accessibility?
Thanks!
accessibility pci-compliance wcag wcag2.0
edited Nov 19 at 18:55
prl
4,1431315
asked Nov 19 at 16:16
Beth
286
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I'm looking for some additional WCAG guidance regarding secure fields needed for PCI (Payment Card Industry) compliance for ecommerce. Payment providers now offer a solution for a higher level of conformance where each payment field (credit card number, CVV, and expiration date) is a DOM-injected iframe, comprising of a label, input, error validation, styling, and focus management. These iframed fields are referred as "secure fields".
We are working with our payment provider to improve their markup, however, if they followed all form and iframe related guidelines, would there be any other concerns regarding accessibility?
Thanks!
accessibility pci-compliance wcag wcag2.0
edited Nov 19 at 18:55
prl
4,1431315
asked Nov 19 at 16:16
Beth
286
I'm looking for some additional WCAG guidance regarding secure fields needed for PCI (Payment Card Industry) compliance for ecommerce. Payment providers now offer a solution for a higher level of conformance where each payment field (credit card number, CVV, and expiration date) is a DOM-injected iframe, comprising of a label, input, error validation, styling, and focus management. These iframed fields are referred as "secure fields".
We are working with our payment provider to improve their markup, however, if they followed all form and iframe related guidelines, would there be any other concerns regarding accessibility?
Thanks!
accessibility pci-compliance wcag wcag2.0
accessibility pci-compliance wcag wcag2.0
edited Nov 19 at 18:55
prl
4,1431315
asked Nov 19 at 16:16
Beth
286
edited Nov 19 at 18:55
prl
4,1431315
asked Nov 19 at 16:16
Beth
286
edited Nov 19 at 18:55
prl
4,1431315
edited Nov 19 at 18:55
prl
4,1431315
edited Nov 19 at 18:55
prl
4,1431315
4,1431315
asked Nov 19 at 16:16
Beth
286
asked Nov 19 at 16:16
Beth
286
asked Nov 19 at 16:16
Beth
286
286
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378722%2fwcag-guidance-regarding-secured-hosted-fields-for-pci-payment-card-industry-co%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53378722%2fwcag-guidance-regarding-secured-hosted-fields-for-pci-payment-card-industry-co%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
