Is window.confirm() accessible?Accessibility of confirm dialog in chromeJavaScript post request like a form...

Is this relativistic mass?

Need help identifying/translating a plaque in Tangier, Morocco

Are cabin dividers used to "hide" the flex of the airplane?

If a centaur druid Wild Shapes into a Giant Elk, do their Charge features stack?

New order #4: World

Shall I use personal or official e-mail account when registering to external websites for work purpose?

Is Social Media Science Fiction?

Can I find out the caloric content of bread by dehydrating it?

Why is the design of haulage companies so “special”?

How to move the player while also allowing forces to affect it

Is it legal to have the "// (c) 2019 John Smith" header in all files when there are hundreds of contributors?

Is domain driven design an anti-SQL pattern?

What do the Banks children have against barley water?

Could a US political party gain complete control over the government by removing checks & balances?

Landlord wants to switch my lease to a "Land contract" to "get back at the city"

Is there a name of the flying bionic bird?

Typesetting a double Over Dot on top of a symbol

Symmetry in quantum mechanics

What causes the sudden spool-up sound from an F-16 when enabling afterburner?

Lied on resume at previous job

Extreme, but not acceptable situation and I can't start the work tomorrow morning

LWC and complex parameters

Why is my log file so massive? 22gb. I am running log backups

Why airport relocation isn't done gradually?



Is window.confirm() accessible?


Accessibility of confirm dialog in chromeJavaScript post request like a form submitjQuery/JavaScript: accessing contents of an iframeCheck if object is a jQuery objectStoring Objects in HTML5 localStorageWhat is the best way to detect a mobile device in jQuery?Open a URL in a new tab (and not a new window) using JavaScriptHow to decide when to use Node.js?How can I add new array elements at the beginning of an array in Javascript?How does Access-Control-Allow-Origin header work?Relation between CommonJS, AMD and RequireJS?






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







6















Are native browser modals like window.confirm, window.alert, and window.prompt accessible, or is it better to implement something custom?










share|improve this question























  • What do you mean with accessible? If you want to give it any style, then no, they are not

    – Marcelo Origoni
    6 hours ago






  • 2





    @MarceloOrigoni I think the OP is talking about people with disabilities.

    – VFDan
    6 hours ago











  • Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

    – Kaiido
    4 hours ago


















6















Are native browser modals like window.confirm, window.alert, and window.prompt accessible, or is it better to implement something custom?










share|improve this question























  • What do you mean with accessible? If you want to give it any style, then no, they are not

    – Marcelo Origoni
    6 hours ago






  • 2





    @MarceloOrigoni I think the OP is talking about people with disabilities.

    – VFDan
    6 hours ago











  • Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

    – Kaiido
    4 hours ago














6












6








6








Are native browser modals like window.confirm, window.alert, and window.prompt accessible, or is it better to implement something custom?










share|improve this question














Are native browser modals like window.confirm, window.alert, and window.prompt accessible, or is it better to implement something custom?







javascript accessibility






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 6 hours ago









skaterdav85skaterdav85

2,41731116




2,41731116













  • What do you mean with accessible? If you want to give it any style, then no, they are not

    – Marcelo Origoni
    6 hours ago






  • 2





    @MarceloOrigoni I think the OP is talking about people with disabilities.

    – VFDan
    6 hours ago











  • Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

    – Kaiido
    4 hours ago



















  • What do you mean with accessible? If you want to give it any style, then no, they are not

    – Marcelo Origoni
    6 hours ago






  • 2





    @MarceloOrigoni I think the OP is talking about people with disabilities.

    – VFDan
    6 hours ago











  • Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

    – Kaiido
    4 hours ago

















What do you mean with accessible? If you want to give it any style, then no, they are not

– Marcelo Origoni
6 hours ago





What do you mean with accessible? If you want to give it any style, then no, they are not

– Marcelo Origoni
6 hours ago




2




2





@MarceloOrigoni I think the OP is talking about people with disabilities.

– VFDan
6 hours ago





@MarceloOrigoni I think the OP is talking about people with disabilities.

– VFDan
6 hours ago













Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

– Kaiido
4 hours ago





Even if screen readers can read these modals'contents, remember they will block your page at least js and in some browsers (e.g Chrome) all UI related content too. These should not be used in modern web.

– Kaiido
4 hours ago












2 Answers
2






active

oldest

votes


















4














There isn't a whole lot of info out there on this, but I believe the answer is yes (for the most part). It seems that previously screen readers didn't have support for alerts/window dialogs but screen readers have come to support these in today's world.



"Although JavaScript pop-up alert boxes were once discouraged by accessibility experts, modern screen readers and browsers provide excellent support for the basic JavaScript alert box."



http://accessibility.psu.edu/scripts/alertboxes/#basic



https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/examples/dialog-modal/alertdialog.html



Reading through the w3 documentation, it seems as though it's more preferred to make your own and specify the appropriate aria attributes






share|improve this answer































    3














    Update: Read the bottom of this answer. According to this answer, they are accessible to most screen-readers, but not JAWS (which as of this December 2017 article has 46% of the market share. So, 46% of the people using screen-readers uses a screen-reader that does not support window.confirm, so it is probably better to make a custom dialog box with the respective aria-* attributes.






    Edit: According to a comment from Travis J., the github issue shows that is was a Chrome bug, which has been patched. However, if you want to keep support for older versions of Chrome, then you can make a custom dialog box, or just make a custom one if you want to add CSS, make more buttons, etc.




    share|improve this answer


























    • The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

      – Travis J
      5 hours ago













    • @TravisJ Thank you, I edited it to add that info.

      – VFDan
      4 hours ago












    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',
    autoActivateHeartbeat: false,
    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
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55583360%2fis-window-confirm-accessible%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    4














    There isn't a whole lot of info out there on this, but I believe the answer is yes (for the most part). It seems that previously screen readers didn't have support for alerts/window dialogs but screen readers have come to support these in today's world.



    "Although JavaScript pop-up alert boxes were once discouraged by accessibility experts, modern screen readers and browsers provide excellent support for the basic JavaScript alert box."



    http://accessibility.psu.edu/scripts/alertboxes/#basic



    https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/examples/dialog-modal/alertdialog.html



    Reading through the w3 documentation, it seems as though it's more preferred to make your own and specify the appropriate aria attributes






    share|improve this answer




























      4














      There isn't a whole lot of info out there on this, but I believe the answer is yes (for the most part). It seems that previously screen readers didn't have support for alerts/window dialogs but screen readers have come to support these in today's world.



      "Although JavaScript pop-up alert boxes were once discouraged by accessibility experts, modern screen readers and browsers provide excellent support for the basic JavaScript alert box."



      http://accessibility.psu.edu/scripts/alertboxes/#basic



      https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/examples/dialog-modal/alertdialog.html



      Reading through the w3 documentation, it seems as though it's more preferred to make your own and specify the appropriate aria attributes






      share|improve this answer


























        4












        4








        4







        There isn't a whole lot of info out there on this, but I believe the answer is yes (for the most part). It seems that previously screen readers didn't have support for alerts/window dialogs but screen readers have come to support these in today's world.



        "Although JavaScript pop-up alert boxes were once discouraged by accessibility experts, modern screen readers and browsers provide excellent support for the basic JavaScript alert box."



        http://accessibility.psu.edu/scripts/alertboxes/#basic



        https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/examples/dialog-modal/alertdialog.html



        Reading through the w3 documentation, it seems as though it's more preferred to make your own and specify the appropriate aria attributes






        share|improve this answer













        There isn't a whole lot of info out there on this, but I believe the answer is yes (for the most part). It seems that previously screen readers didn't have support for alerts/window dialogs but screen readers have come to support these in today's world.



        "Although JavaScript pop-up alert boxes were once discouraged by accessibility experts, modern screen readers and browsers provide excellent support for the basic JavaScript alert box."



        http://accessibility.psu.edu/scripts/alertboxes/#basic



        https://www.w3.org/TR/2018/WD-wai-aria-practices-1.2-20180719/examples/dialog-modal/alertdialog.html



        Reading through the w3 documentation, it seems as though it's more preferred to make your own and specify the appropriate aria attributes







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered 6 hours ago









        mwilsonmwilson

        3,28432148




        3,28432148

























            3














            Update: Read the bottom of this answer. According to this answer, they are accessible to most screen-readers, but not JAWS (which as of this December 2017 article has 46% of the market share. So, 46% of the people using screen-readers uses a screen-reader that does not support window.confirm, so it is probably better to make a custom dialog box with the respective aria-* attributes.






            Edit: According to a comment from Travis J., the github issue shows that is was a Chrome bug, which has been patched. However, if you want to keep support for older versions of Chrome, then you can make a custom dialog box, or just make a custom one if you want to add CSS, make more buttons, etc.




            share|improve this answer


























            • The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

              – Travis J
              5 hours ago













            • @TravisJ Thank you, I edited it to add that info.

              – VFDan
              4 hours ago
















            3














            Update: Read the bottom of this answer. According to this answer, they are accessible to most screen-readers, but not JAWS (which as of this December 2017 article has 46% of the market share. So, 46% of the people using screen-readers uses a screen-reader that does not support window.confirm, so it is probably better to make a custom dialog box with the respective aria-* attributes.






            Edit: According to a comment from Travis J., the github issue shows that is was a Chrome bug, which has been patched. However, if you want to keep support for older versions of Chrome, then you can make a custom dialog box, or just make a custom one if you want to add CSS, make more buttons, etc.




            share|improve this answer


























            • The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

              – Travis J
              5 hours ago













            • @TravisJ Thank you, I edited it to add that info.

              – VFDan
              4 hours ago














            3












            3








            3







            Update: Read the bottom of this answer. According to this answer, they are accessible to most screen-readers, but not JAWS (which as of this December 2017 article has 46% of the market share. So, 46% of the people using screen-readers uses a screen-reader that does not support window.confirm, so it is probably better to make a custom dialog box with the respective aria-* attributes.






            Edit: According to a comment from Travis J., the github issue shows that is was a Chrome bug, which has been patched. However, if you want to keep support for older versions of Chrome, then you can make a custom dialog box, or just make a custom one if you want to add CSS, make more buttons, etc.




            share|improve this answer















            Update: Read the bottom of this answer. According to this answer, they are accessible to most screen-readers, but not JAWS (which as of this December 2017 article has 46% of the market share. So, 46% of the people using screen-readers uses a screen-reader that does not support window.confirm, so it is probably better to make a custom dialog box with the respective aria-* attributes.






            Edit: According to a comment from Travis J., the github issue shows that is was a Chrome bug, which has been patched. However, if you want to keep support for older versions of Chrome, then you can make a custom dialog box, or just make a custom one if you want to add CSS, make more buttons, etc.





            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 4 hours ago

























            answered 6 hours ago









            VFDanVFDan

            303213




            303213













            • The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

              – Travis J
              5 hours ago













            • @TravisJ Thank you, I edited it to add that info.

              – VFDan
              4 hours ago



















            • The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

              – Travis J
              5 hours ago













            • @TravisJ Thank you, I edited it to add that info.

              – VFDan
              4 hours ago

















            The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

            – Travis J
            5 hours ago







            The JAWS github issue for this from 2017, github.com/FreedomScientific/VFO-standards-support/issues/16, indicates it was a chrome bug, which chrome subsequently patched, bugs.chromium.org/p/chromium/issues/detail?id=779501. While using aria attributes are a good idea, I think that the information in the preamble here may be citing old sources.

            – Travis J
            5 hours ago















            @TravisJ Thank you, I edited it to add that info.

            – VFDan
            4 hours ago





            @TravisJ Thank you, I edited it to add that info.

            – VFDan
            4 hours ago


















            draft saved

            draft discarded




















































            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55583360%2fis-window-confirm-accessible%23new-answer', 'question_page');
            }
            );

            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







            Popular posts from this blog

            “%fieldName is a required field.”, in Magento2 REST API Call for GET Method Type The Next...

            How to change City field to a dropdown in Checkout step Magento 2Magento 2 : How to change UI field(s)...

            變成蝙蝠會怎樣? 參考資料 外部連結 导航菜单Thomas Nagel, "What is it like to be a...