{"id":1690,"date":"2023-11-01T06:02:23","date_gmt":"2023-11-01T06:02:23","guid":{"rendered":"http:\/\/13.235.74.208\/?p=1690"},"modified":"2023-12-06T11:54:06","modified_gmt":"2023-12-06T11:54:06","slug":"automated-test-result-to-improve-accessibility","status":"publish","type":"post","link":"https:\/\/kryobot.com\/?p=1690","title":{"rendered":"Automated Test Result to Improve Accessibility"},"content":{"rendered":"\t\t<div data-elementor-type=\"wp-post\" data-elementor-id=\"1690\" class=\"elementor elementor-1690\" data-elementor-post-type=\"post\">\n\t\t\t\t\t\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-3250443c elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"3250443c\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-68fc473e\" data-id=\"68fc473e\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-fa86a4f elementor-widget elementor-widget-text-editor\" data-id=\"fa86a4f\" data-element_type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<style>\/*! elementor - v3.13.3 - 28-05-2023 *\/\n.elementor-widget-text-editor.elementor-drop-cap-view-stacked .elementor-drop-cap{background-color:#69727d;color:#fff}.elementor-widget-text-editor.elementor-drop-cap-view-framed .elementor-drop-cap{color:#69727d;border:3px solid;background-color:transparent}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap{margin-top:8px}.elementor-widget-text-editor:not(.elementor-drop-cap-view-default) .elementor-drop-cap-letter{width:1em;height:1em}.elementor-widget-text-editor .elementor-drop-cap{float:left;text-align:center;line-height:1;font-size:50px}.elementor-widget-text-editor .elementor-drop-cap-letter{display:inline-block}<\/style>\t\t\t\t<!-- wp:paragraph -->\n<p>Accessibility is a crucial aspect of web and app development. Ensuring that digital content is<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>accessible to all users, including those with disabilities, is not only a legal requirement in many<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>places but also a moral imperative. One effective way to achieve accessibility is through<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>automated testing tools like WAVE, AXE or Lighthouse that can provide actionable insights like<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>missing alt text, low contrast or keyboard accessibility and improve the user experience for<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>everyone. To check the content behavior and response to different user interactions and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>preferences, manual testing techniques like navigation, zooming, and resizing also can be used.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>In this blog post, we will explore the importance of automated test results in enhancing<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>accessibility and provide a comprehensive guide for developers and testers.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>What is digital accessibility?<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>digital accessibility is the practice of designing and developing digital content and technologies<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>in a way that ensures equal access and usability for people with disabilities. It aims to remove<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>barriers that may prevent individuals with disabilities from using digital products and services<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>effectively. By prioritizing accessibility, organizations can not only avoid legal troubles but also<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>contribute to a more inclusive and equitable society.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>Challenges associated with manual testing<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Manual testing often relies on human judgment, making it subjective. It can be labour-intensive<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>and time-consuming. Manual testing often focuses on common use cases, which may not cover<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>all possible user scenarios. Due to resource constraints, manual testing may not cover all aspects<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>of a website or application and we cannot scale it well, making it challenging to test frequently<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>updated content or applications. Testers can make mistakes or overlook issues during manual<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>testing. Effective manual testing requires testers to have expertise in accessibility guidelines and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>assistive technologies. Finding and training testers with this expertise can be a challenge and it<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>can be costly. In some cases, accessibility issues need to be identified and fixed quickly, such as<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>during a website launch or when responding to user complaints. Manual testing may not always<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>provide timely results. Websites and applications with dynamic content that change based on<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>user input or other factors can be challenging to test manually.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>Why automated testing for accessibility<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p><strong>Efficiency<\/strong>: Automated tests can execute much faster than manual tests, allowing for quicker<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>feedback on the quality of the software. This speed is particularly useful in agile and continuous<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>integration\/continuous deployment (CI\/CD) environments, where rapid feedback is crucial.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Time-Saving<\/strong>: Automated testing reduces the need for manual testers to perform repetitive, time-<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>consuming, and monotonous tasks. This frees up human testers to focus on more creative and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>exploratory testing.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Enhanced Test Coverage<\/strong>: Automated tests can cover a wide range of test scenarios, including<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>edge cases and stress testing, which might be impractical to perform manually.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Accuracy:<\/strong>&nbsp;Automated tests follow predefined scripts and instructions, minimizing human errors.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>They are less prone to overlook issues that can occur due to tester fatigue or oversight.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Resource Savings:<\/strong>&nbsp;Automated testing reduces the need for manual testers to perform repetitive,<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>time-consuming, and monotonous tasks.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Continuous Integration<\/strong>: Automated tests can be integrated into CI\/CD pipelines, allowing for<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>automated testing after every code change. This helps catch issues early in the development<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>process, reducing the cost and effort required to fix them later.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Parallel Testing<\/strong>: Automated tests can be run in parallel on different environments and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>configurations, which accelerates testing for various platforms, browsers, and devices<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>simultaneously.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Data-Driven Testing:<\/strong>&nbsp;Automated tests can be parameterized to run with different sets of test<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>data, helping to evaluate the behaviour of the software under various conditions.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Reusable Test Scripts:<\/strong>&nbsp;Once created, automated test scripts can be reused across different<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>versions of the software which saves time and effort in the long run.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p><strong>Logging and Reporting:<\/strong>&nbsp;Automated testing tools generate detailed logs and reports, making it<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>How to leverage automated test results from accessibility checks<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong> to achieve sustainable digital accessibility transformation?<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Without proper guidance on what to do with the results increase in the amount of accessibility<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>testing does not correlate with the increased accessibility of the digital world. To tackle this<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>problem, development teams should make the most of the output from automated accessibility<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>testing. Only then can they effectively use the results and it requires a more strategic approach.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>Quality gates<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>Quality gates are an essential part of continuous integration\/continuous deployment (CI\/CD)<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>pipelines and other software development workflows. Quality gates in automated testing are<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>predefined checkpoints. Quality gates help to check if there are no linting errors if the project has<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>no errors or if all test cases have passed.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>Two different ways that the quality gate can operate a\u00a0<strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">soft check<\/mark><\/strong>\u00a0and a\u00a0<strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">hard assertion<\/mark><\/strong>. A soft<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>check is relatively simpler than a hard assertion, in that It looks at whether or not the<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>accessibility checks were run, and then the test passes. In contrast, the hard assertion fails if it<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>finds even ONE issue.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>The creation of gates that are data-driven, can help make a more effective gate that matches your<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>accessibility goals. <\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:spacer {\"height\":\"45px\"} -->\n<div style=\"height:45px\" aria-hidden=\"true\" class=\"wp-block-spacer\"><\/div>\n<!-- \/wp:spacer -->\n\n<!-- wp:heading {\"level\":5} -->\n<h5 class=\"wp-block-heading\"><strong>Fixing bugs<\/strong><\/h5>\n<!-- \/wp:heading -->\n\n<!-- wp:paragraph -->\n<p>it is necessary to be able to prioritize accessibility test results to apply limited resources to<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>seemingly unlimited bugs to fix them in as efficient and effective a way as possible. Here context<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>is a top-level filter, attacking bugs and blockers that exist in critical user flows and high-traffic<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>pages or screens. Another filter is Prioritising bugs depending on their severity. The third filter is<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>the level of effort to implement affix. This way a developer always has a result that clearly states<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>what\u2019s wrong, where\u2019s it wrong, and how to fix it. To prevent similar issues from recurring,<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>several free tools exist in the community which ultimately improve downstream accessibility<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>while maintaining development velocity, the\u00a0<strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">accessibility browser extension<\/mark><\/strong>\u00a0is one such family<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>of tools. The browser extensions allow a developer to quickly scan a page in the browser and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>identify issues on the page. Another group of free tools is\u00a0<strong><mark style=\"background-color:rgba(0, 0, 0, 0)\" class=\"has-inline-color has-vivid-red-color\">lintres<\/mark><\/strong>. It\u2019s fully automated and<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>requires little to no effort from the developer. Browser extensions and liners help the<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>development team to find and fix accessibility bugs immediately.<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>Even so, the actual impact on the overall accessibility empowers us to execute tests inefficient<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>ways and enables us to use the test results to drive rapid remediation, govern the overall quality<\/p>\n<!-- \/wp:paragraph -->\n\n<!-- wp:paragraph -->\n<p>and put things in place to prevent regression.<\/p>\n<!-- \/wp:paragraph -->\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t<section class=\"elementor-section elementor-top-section elementor-element elementor-element-4fcece8 elementor-section-boxed elementor-section-height-default elementor-section-height-default\" data-id=\"4fcece8\" data-element_type=\"section\">\n\t\t\t\t\t\t<div class=\"elementor-container elementor-column-gap-default\">\n\t\t\t\t\t<div class=\"elementor-column elementor-col-100 elementor-top-column elementor-element elementor-element-7ef7a3f\" data-id=\"7ef7a3f\" data-element_type=\"column\">\n\t\t\t<div class=\"elementor-widget-wrap elementor-element-populated\">\n\t\t\t\t\t\t\t\t<div class=\"elementor-element elementor-element-6423e3d elementor-widget elementor-widget-mfn_blog_teaser\" data-id=\"6423e3d\" data-element_type=\"widget\" data-widget_type=\"mfn_blog_teaser.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t<div class=\"blog-teaser \"><ul class=\"teaser-wrapper\"><li class=\"post-3330 post type-post status-publish format-standard hentry category-uncategorized\"><div class=\"photo-wrapper scale-with-grid\"><\/div><div class=\"desc-wrapper\"><div class=\"desc\"><div class=\"post-meta clearfix\"><span class=\"author\"><span class=\"label\">Published by <\/span><i class=\"icon-user\" aria-hidden=\"true\"><\/i> <a href=\"https:\/\/kryobot.com\/?author=1\">user<\/a><\/span> <span class=\"date\"><span class=\"label\">on <\/span><i class=\"icon-clock\" aria-hidden=\"true\"><\/i> <span class=\"post-date\">October 17, 2026<\/span><\/span><span class=\"comments\"><i class=\"icon-comment-empty-fa\" aria-label=\"comments number\"><\/i> <a href=\"https:\/\/kryobot.com\/?p=3330#respond\" class=\"post-comments\">0<\/a><\/span><\/div><div class=\"post-title\"><h3><a href=\"https:\/\/kryobot.com\/?p=3330\">Inspanningen leveren voor succes met thorfortune en de beste strategie\u00ebn<\/a><\/h3><\/div><\/div><\/div><\/li><li class=\"post-3329 post type-post status-publish format-standard hentry category-uncategorized\"><div class=\"photo-wrapper scale-with-grid\"><\/div><div class=\"desc-wrapper\"><div class=\"desc\"><div class=\"post-meta clearfix\"><span class=\"author\"><span class=\"label\">Published by <\/span><i class=\"icon-user\" aria-hidden=\"true\"><\/i> <a href=\"https:\/\/kryobot.com\/?author=1\">user<\/a><\/span> <span class=\"date\"><span class=\"label\">on <\/span><i class=\"icon-clock\" aria-hidden=\"true\"><\/i> <span class=\"post-date\">October 17, 2026<\/span><\/span><span class=\"comments\"><i class=\"icon-comment-empty-fa\" aria-label=\"comments number\"><\/i> <a href=\"https:\/\/kryobot.com\/?p=3329#respond\" class=\"post-comments\">0<\/a><\/span><\/div><div class=\"post-title\"><h4><a href=\"https:\/\/kryobot.com\/?p=3329\">Effektive Wege zum Ziel mit my-empires.de und nachhaltiger Unternehmensentwicklung f\u00fcr langfristigen Erfolg<\/a><\/h4><\/div><\/div><\/div><\/li><li class=\"post-3327 post type-post status-publish format-standard hentry category-uncategorized\"><div class=\"photo-wrapper scale-with-grid\"><\/div><div class=\"desc-wrapper\"><div class=\"desc\"><div class=\"post-meta clearfix\"><span class=\"author\"><span class=\"label\">Published by <\/span><i class=\"icon-user\" aria-hidden=\"true\"><\/i> <a href=\"https:\/\/kryobot.com\/?author=1\">user<\/a><\/span> <span class=\"date\"><span class=\"label\">on <\/span><i class=\"icon-clock\" aria-hidden=\"true\"><\/i> <span class=\"post-date\">October 17, 2026<\/span><\/span><span class=\"comments\"><i class=\"icon-comment-empty-fa\" aria-label=\"comments number\"><\/i> <a href=\"https:\/\/kryobot.com\/?p=3327#respond\" class=\"post-comments\">0<\/a><\/span><\/div><div class=\"post-title\"><h4><a href=\"https:\/\/kryobot.com\/?p=3327\">Gambling options from classic slots to live dealers via https:\/\/jokas-casino-au.com offer varied gameplay<\/a><\/h4><\/div><\/div><\/div><\/li><\/ul><\/div>\n\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/section>\n\t\t\t\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Accessibility is a crucial aspect of web and app development. Ensuring that digital content is accessible to all users, including those with disabilities, is not only<span class=\"excerpt-hellip\"> [\u2026]<\/span><\/p>\n","protected":false},"author":1,"featured_media":1605,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_uf_show_specific_survey":0,"_uf_disable_surveys":false,"_joinchat":[],"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1690","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/posts\/1690","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/kryobot.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1690"}],"version-history":[{"count":26,"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/posts\/1690\/revisions"}],"predecessor-version":[{"id":1909,"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/posts\/1690\/revisions\/1909"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kryobot.com\/index.php?rest_route=\/wp\/v2\/media\/1605"}],"wp:attachment":[{"href":"https:\/\/kryobot.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1690"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kryobot.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1690"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kryobot.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1690"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}