{"id":237436,"date":"2026-05-21T08:07:03","date_gmt":"2026-05-21T08:07:03","guid":{"rendered":"https:\/\/osmosys.co\/uk\/?p=237436"},"modified":"2026-05-21T08:07:06","modified_gmt":"2026-05-21T08:07:06","slug":"accessibility-in-power-apps-dynamics-365-enterprise-checklist","status":"publish","type":"post","link":"https:\/\/osmosys.co\/uk\/accessibility-in-power-apps-dynamics-365-enterprise-checklist\/","title":{"rendered":"Accessibility in Power Apps and Dynamics 365: A Practical Enterprise Checklist"},"content":{"rendered":"
<\/div>\n

For many enterprise teams<\/a>, accessibility still gets discussed too late.<\/p>\n\n\n\n

The app is already built.
The forms are already configured.
The dashboards are already approved.
The workflow is already live.
Then someone asks: can everyone actually use this?<\/p>\n\n\n\n

That is the wrong moment to discover accessibility gaps.<\/p>\n\n\n\n

On 21 May 2026<\/strong>, Global Accessibility Awareness Day puts digital access and inclusion back in focus. The purpose of GAAD is to get people talking, thinking, and learning about digital access and inclusion, especially for people with disabilities and impairments. In the UK, Digital Accessibility Week 2026 is also focused on designing, developing, and delivering accessible digital services.<\/p>\n\n\n\n

For organisations using Microsoft business applications, this is the right time to review accessibility in Power Apps<\/strong> and Dynamics 365 accessibility<\/strong> more seriously.<\/p>\n\n\n\n

Because accessibility is not only about meeting a standard.<\/p>\n\n\n\n

It is about whether employees, customers, service teams, finance users, sales teams, operations managers, and frontline workers can use business systems with confidence.<\/p>\n\n\n\n

When enterprise applications are hard to read, hard to navigate, hard to understand, or impossible to use without a mouse, accessibility becomes a productivity issue. It becomes an adoption issue. And in some cases, it becomes a risk issue.<\/p>\n\n\n\n

That is why accessibility should be treated as part of enterprise application quality.<\/p>\n\n\n\n

Why Accessibility Matters in Enterprise Apps<\/h2>\n\n\n\n

Enterprise applications are not optional tools for many users. They are where work happens.<\/p>\n\n\n\n

A sales user updates an opportunity in Dynamics 365.
A field worker submits a site update through Power Apps.
A finance team reviews approvals.
A service agent handles customer information.
A manager checks dashboards before making a decision.<\/p>\n\n\n\n

If these systems are not accessible, people are not just inconvenienced. They may be blocked from doing their work properly.<\/p>\n\n\n\n

The World Wide Web Consortium explains that WCAG 2.2 covers a wide range of recommendations for making web content more accessible, including support for people with visual, auditory, physical, speech, cognitive, language, learning, and neurological disabilities. W3C also notes that following accessibility guidelines often improves usability for users in general.<\/p>\n\n\n\n

That point matters for business applications.<\/p>\n\n\n\n

Accessible design helps users who rely on assistive technologies. But it also helps users who are tired, working on smaller screens, using touch devices, dealing with temporary injuries, working in poor lighting, or navigating complex workflows under time pressure.<\/p>\n\n\n\n

So the business case is simple:<\/p>\n\n\n\n

Accessible apps are usually better apps.<\/p>\n\n\n\n

Accessibility in Power Apps: What Microsoft Already Emphasises<\/h2>\n\n\n\n

Microsoft\u2019s guidance for accessible canvas apps is clear: accessible apps allow users with vision, hearing, and other impairments to use the app successfully, and accessibility improvements increase usability for all users. Microsoft recommends using the Accessibility Checker in Power Apps to review potential issues.<\/p>\n\n\n\n

Microsoft\u2019s Power Apps accessibility guidance also calls out practical design areas such as:<\/p>\n\n\n\n

\u2192 visible elements and readable text
\u2192 labelled input elements
\u2192 sufficient colour contrast
\u2192 logical screen layout
\u2192 responsive design
\u2192 keyboard-only use
\u2192 screen reader support
\u2192 correct control structure
\u2192 captions and transcripts for multimedia
\u2192 alternative input methods where needed<\/p>\n\n\n\n

This is helpful because many accessibility issues in Power Apps are not caused by bad intent. They are caused by small design decisions that go unchecked.<\/p>\n\n\n\n

A button looks like text.
An icon has no accessible label.
A colour-coded status has no text cue.
A custom screen has confusing tab order.
A form works visually but not with a screen reader.<\/p>\n\n\n\n

These are fixable issues. But they need to be part of the design and review process, not an afterthought.<\/p>\n\n\n\n

\n\n\n\n

A Practical Enterprise Checklist for Power Apps and Dynamics 365 Accessibility<\/h1>\n\n\n\n

1. Start With Accessibility as a Requirement, Not a Final Review<\/h2>\n\n\n\n

The first mistake is treating accessibility as a testing task only.<\/p>\n\n\n\n

Accessibility should be discussed at the beginning of a Power Apps or Dynamics 365 project, along with security, data, workflow, reporting, and user adoption.<\/p>\n\n\n\n

Before designing or configuring the app, ask:<\/p>\n\n\n\n

\u2192 Who will use this application?
\u2192 Will users access it on desktop, tablet, mobile, or shared devices?
\u2192 Will any users rely on keyboard navigation or screen readers?
\u2192 Are there users with visual, motor, hearing, cognitive, or temporary accessibility needs?
\u2192 Is this app used internally, externally, or by public-sector users?
\u2192 Are there accessibility expectations from procurement, governance, or compliance teams?<\/p>\n\n\n\n

For UK organisations, this question becomes especially important where systems support public-sector services, regulated processes, employee portals, or customer-facing digital services.<\/p>\n\n\n\n

GOV.UK guidance states that UK public sector websites and mobile apps must be made more accessible by making them perceivable, operable, understandable, and robust, and that meeting WCAG 2.2 AA is part of meeting legal requirements for public sector websites and mobile apps.<\/p>\n\n\n\n

Even when a private-sector organisation is not directly under the same public-sector accessibility regulations, accessibility still supports better inclusion, better usability, and stronger governance.<\/p>\n\n\n\n

2. Check Colour Contrast Before the Brand Theme Goes Too Far<\/h2>\n\n\n\n

Colour is one of the fastest ways to make an enterprise app look polished. It is also one of the fastest ways to make it inaccessible.<\/p>\n\n\n\n

Microsoft\u2019s Power Apps guidance says text and background should have a contrast ratio of at least 4.5:1<\/strong>, large text should have at least 3:1<\/strong>, and non-text components such as icons and borders should have at least 3:1<\/strong> contrast with surrounding colours. It also warns against conveying information using colour alone.<\/p>\n\n\n\n

This matters for apps that use colours to show:<\/p>\n\n\n\n

\u2192 approval status
\u2192 risk level
\u2192 overdue actions
\u2192 priority
\u2192 service status
\u2192 financial exceptions
\u2192 compliance gaps
\u2192 task ownership<\/p>\n\n\n\n

A red\/green indicator may look clear to some users, but not to everyone.<\/p>\n\n\n\n

Better practice:<\/p>\n\n\n\n

\u2192 use colour plus text
\u2192 use icons plus labels
\u2192 keep error and success messages clearly written
\u2192 ensure buttons and borders are visible
\u2192 check hover, pressed, focus, and disabled states
\u2192 test the app in light and dark environments where relevant<\/p>\n\n\n\n

Accessibility should not weaken the brand. It should make the brand usable.<\/p>\n\n\n\n

3. Make Forms Easy to Understand and Complete<\/h2>\n\n\n\n

Power Apps and Dynamics 365 forms are often where accessibility succeeds or fails.<\/p>\n\n\n\n

A form may look clean, but users can still struggle if:<\/p>\n\n\n\n

\u2192 field labels are unclear
\u2192 required fields are not obvious
\u2192 error messages are vague
\u2192 sections are too dense
\u2192 related fields are not grouped logically
\u2192 instructions appear only after a mistake
\u2192 the form depends too heavily on placeholders
\u2192 users must enter the same information repeatedly<\/p>\n\n\n\n

WCAG 2.2 includes criteria related to accessible authentication and reducing redundant entry, which is especially relevant for form-heavy business applications.<\/p>\n\n\n\n

For enterprise apps, the principle is straightforward:<\/p>\n\n\n\n

Do not make users work harder than necessary to complete a business process.<\/p>\n\n\n\n

Better practice:<\/p>\n\n\n\n

\u2192 use clear labels, not internal system terms
\u2192 group related fields together
\u2192 explain why sensitive or unusual data is being requested
\u2192 mark required fields clearly
\u2192 place help text near the relevant field
\u2192 write error messages that explain how to fix the issue
\u2192 avoid asking users to re-enter information the system already knows
\u2192 keep forms as short as the process allows<\/p>\n\n\n\n

This improves accessibility and reduces user frustration.<\/p>\n\n\n\n

4. Design for Keyboard Navigation<\/h2>\n\n\n\n

Some users cannot use a mouse. Some users prefer not to. Some enterprise users work faster with keyboard-based navigation.<\/p>\n\n\n\n

Microsoft recommends testing Power Apps so they can be used by keyboard only, with or without a screen reader. It also highlights the importance of logical tab order and recommends using TabIndex carefully.<\/p>\n\n\n\n

Keyboard accessibility matters in:<\/p>\n\n\n\n

\u2192 approval apps
\u2192 service management apps
\u2192 HR and finance workflows
\u2192 data entry screens
\u2192 case management forms
\u2192 field service admin screens
\u2192 dashboards with filters and controls<\/p>\n\n\n\n

A practical keyboard check should answer:<\/p>\n\n\n\n

\u2192 Can the user move through the screen logically using Tab?
\u2192 Is the current focus clearly visible?
\u2192 Can all interactive controls be reached?
\u2192 Can the user operate dropdowns, buttons, menus, and forms without a mouse?
\u2192 Does the tab order match the visual order?
\u2192 Can the user escape modals, popups, and overlays?<\/p>\n\n\n\n

Microsoft\u2019s Accessibility Checker can detect screen-reader and keyboard-related issues, including missing accessible labels and focus issues.<\/p>\n\n\n\n

This should be part of every Power Apps review before go-live.<\/p>\n\n\n\n

5. Use Accessible Labels Properly<\/h2>\n\n\n\n

Accessible labels are small details with major impact.<\/p>\n\n\n\n

Microsoft\u2019s Power Apps guidance states that input controls should have accessible labels, and that images or icons used as buttons should have accessible labels that describe their purpose. Decorative images should not be read unnecessarily by screen readers.<\/p>\n\n\n\n

This is especially important in enterprise apps where icons are commonly used for:<\/p>\n\n\n\n

\u2192 edit
\u2192 delete
\u2192 approve
\u2192 reject
\u2192 submit
\u2192 search
\u2192 filter
\u2192 download
\u2192 open record
\u2192 escalate issue<\/p>\n\n\n\n

A visual icon may be obvious to one user and meaningless to another.<\/p>\n\n\n\n

Better practice:<\/p>\n\n\n\n

\u2192 write labels based on action, not appearance
\u2192 use \u201cSubmit inspection report\u201d instead of \u201cblue button\u201d
\u2192 use \u201cOpen customer record\u201d instead of \u201carrow icon\u201d
\u2192 avoid vague labels like \u201cclick here\u201d or \u201cicon\u201d
\u2192 check whether labels make sense out of visual context<\/p>\n\n\n\n

Accessible labels are not only a technical fix. They are part of clear communication.<\/p>\n\n\n\n

6. Do Not Rely on Visual Layout Alone<\/h2>\n\n\n\n

Enterprise users often scan screens visually. Screen reader users experience the same screen differently.<\/p>\n\n\n\n

That means structure matters.<\/p>\n\n\n\n

Microsoft recommends using the right controls and grouping related content in containers so screen reader users can understand the structure of the app. It also recommends including at least one heading on each screen and using buttons instead of labels for interactive text.<\/p>\n\n\n\n

For Power Apps and Dynamics 365, this means:<\/p>\n\n\n\n

\u2192 screens should have meaningful names
\u2192 sections should use clear headings
\u2192 controls should match their actual function
\u2192 clickable text should be implemented as an interactive control
\u2192 related fields should be grouped clearly
\u2192 decorative elements should not interrupt screen reader flow<\/p>\n\n\n\n

This is where many highly customised apps become difficult to use. The more custom the experience, the more intentional the structure needs to be.<\/p>\n\n\n\n

7. Make Dashboards and Charts Understandable Beyond Colour<\/h2>\n\n\n\n

Dashboards are common in Dynamics 365 and Power Platform environments, but they can create accessibility problems when they rely too heavily on colour, small labels, dense visuals, or unclear chart legends.<\/p>\n\n\n\n

An accessible dashboard should help users understand the message without forcing them to decode the design.<\/p>\n\n\n\n

Better practice:<\/p>\n\n\n\n

\u2192 use clear chart titles
\u2192 avoid colour-only status meaning
\u2192 include labels or values where useful
\u2192 provide summaries for complex visuals
\u2192 avoid tiny text in chart legends
\u2192 keep dashboard filters keyboard-accessible
\u2192 check contrast for chart elements
\u2192 make sure the key insight is written, not only visual<\/p>\n\n\n\n

For executive dashboards, this is especially important. Accessibility is not only about whether the dashboard technically loads. It is about whether the user can understand and act on it.<\/p>\n\n\n\n

8. Test With Real Assistive Scenarios<\/h2>\n\n\n\n

Automated tools are useful, but they cannot tell the whole story.<\/p>\n\n\n\n

Microsoft\u2019s Accessibility Checker in Power Apps helps identify potential issues and classifies them as errors, warnings, or tips. Errors are issues that can make an app difficult or impossible to use and understand for users with disabilities. Warnings and tips help improve the experience further.<\/p>\n\n\n\n

But enterprise teams should go further.<\/p>\n\n\n\n

Test scenarios should include:<\/p>\n\n\n\n

\u2192 keyboard-only navigation
\u2192 screen reader review
\u2192 zoomed-in view
\u2192 mobile access
\u2192 low-light or high-glare environments
\u2192 users with slower reading speed
\u2192 users completing tasks under time pressure
\u2192 error recovery and form correction<\/p>\n\n\n\n

The goal is not just to pass a checklist. The goal is to know whether users can complete real business tasks.<\/p>\n\n\n\n

9. Include Accessibility in Governance and Change Control<\/h2>\n\n\n\n

Accessibility should not disappear after go-live.<\/p>\n\n\n\n

Every new screen, field, dashboard, automation, form customisation, or app update can introduce new issues.<\/p>\n\n\n\n

That is why accessibility belongs in governance.<\/p>\n\n\n\n

For Power Apps and Dynamics 365 teams, this means:<\/p>\n\n\n\n

\u2192 accessibility checks before production release
\u2192 accessibility review during major UI changes
\u2192 design standards for colour, labels, forms, and controls
\u2192 reusable accessible components where possible
\u2192 documentation for makers and admins
\u2192 accessibility ownership in the Centre of Excellence or governance model
\u2192 periodic review of high-use apps and critical workflows<\/p>\n\n\n\n

Microsoft\u2019s Dynamics 365 accessibility training module highlights that minor changes can make a substantial difference for accessibility and that tools can help determine accessibility issues.<\/p>\n\n\n\n

In enterprise environments, those minor changes need a repeatable process.<\/p>\n\n\n\n

10. Connect Accessibility With Adoption<\/h2>\n\n\n\n

Accessibility is often framed as a compliance responsibility. But it is also an adoption lever.<\/p>\n\n\n\n

If an app is easier to read, easier to navigate, easier to understand, and easier to complete, more people can use it properly.<\/p>\n\n\n\n

That improves:<\/p>\n\n\n\n

\u2192 user confidence
\u2192 data quality<\/a>
\u2192 process completion
\u2192 training efficiency
\u2192 employee experience
\u2192 customer experience
\u2192 long-term platform trust<\/p>\n\n\n\n

This is especially important for organisations investing in low-code platforms. Power Apps enables faster app creation, but speed should not come at the cost of usability or inclusion.<\/p>\n\n\n\n

The best enterprise apps are not just functional.<\/p>\n\n\n\n

They are usable by the widest practical range of users.<\/p>\n\n\n\n

\n\n\n\n

Practical Accessibility Checklist for Enterprise Teams<\/h1>\n\n\n\n

Use this checklist before publishing or updating Power Apps and Dynamics 365 experiences.<\/p>\n\n\n\n

Design and Layout<\/h2>\n\n\n\n

\u2192 Is every screen easy to understand at a glance?
\u2192 Is there a clear heading on each screen?
\u2192 Are related fields grouped logically?
\u2192 Is the layout responsive for different devices and zoom levels?
\u2192 Is the visual order aligned with the reading and tab order?<\/p>\n\n\n\n

Colour and Contrast<\/h2>\n\n\n\n

\u2192 Does text have sufficient contrast against the background?
\u2192 Do icons, borders, and focus indicators have enough contrast?
\u2192 Is colour supported by text, icons, labels, or patterns?
\u2192 Are error, warning, and success states understandable without colour alone?<\/p>\n\n\n\n

Forms and Inputs<\/h2>\n\n\n\n

\u2192 Are all fields clearly labelled?
\u2192 Are required fields easy to identify?
\u2192 Are error messages specific and helpful?
\u2192 Is repeated data entry avoided where possible?
\u2192 Are instructions placed close to the relevant field?<\/p>\n\n\n\n

Keyboard and Focus<\/h2>\n\n\n\n

\u2192 Can the full process be completed without a mouse?
\u2192 Is the focus state visible at all times?
\u2192 Does tab order follow a logical sequence?
\u2192 Can users access and exit popups, menus, and modals?
\u2192 Are all interactive controls reachable by keyboard?<\/p>\n\n\n\n

Screen Reader Support<\/h2>\n\n\n\n

\u2192 Do buttons and icons have meaningful accessible labels?
\u2192 Are decorative images hidden from assistive technologies where appropriate?
\u2192 Are screen names and headings useful?
\u2192 Are dynamic changes announced where needed?
\u2192 Are controls used according to their intended purpose?<\/p>\n\n\n\n

Dashboards and Reports<\/h2>\n\n\n\n

\u2192 Are charts supported by text summaries or clear labels?
\u2192 Are legends readable?
\u2192 Do filters and controls work with keyboard navigation?
\u2192 Is the key insight understandable without relying only on colour?
\u2192 Are dashboard layouts readable on different screens?<\/p>\n\n\n\n

Governance<\/h2>\n\n\n\n

\u2192 Is accessibility checked before go-live?
\u2192 Is accessibility included in release review?
\u2192 Are makers trained on accessible design basics?
\u2192 Are reusable components accessible by default?
\u2192 Is there a process to fix accessibility feedback after release?<\/p>\n\n\n\n

\n\n\n\n

Final Thought<\/h1>\n\n\n\n

Accessibility in Power Apps and Dynamics 365 is not a cosmetic detail.<\/p>\n\n\n\n

It is part of enterprise application quality.<\/p>\n\n\n\n

It affects whether people can complete tasks, trust the system, adopt the process, and use business applications without unnecessary barriers.<\/p>\n\n\n\n

GAAD 2026 is a useful reminder, but accessibility should not be a once-a-year conversation. It should be part of how enterprise apps are planned, designed, tested, governed, and improved.<\/p>\n\n\n\n

For UK organisations, the direction is clear. Digital accessibility is no longer only a specialist topic. It is relevant to product owners, developers, admins, testers, service owners, compliance teams, and business leaders.<\/p>\n\n\n\n

The practical step is simple: review the apps your teams already depend on.<\/p>\n\n\n\n

Start with the screens people use every day.
Check the forms that carry critical data.
Review the dashboards leaders rely on.
Test keyboard navigation.
Run the Accessibility Checker.
Listen to users who experience barriers.<\/p>\n\n\n\n

Because inclusive enterprise apps do not happen by accident.<\/p>\n\n\n\n

They are designed, tested, governed, and improved with intention.<\/p>\n\n\n\n

\n\n\n\n
\"Accessibility<\/a><\/figure>\n\n\n\n
\n\n\n\n

FAQ<\/h1>\n\n\n
\n
\n
\n

What is accessibility in Power Apps?<\/h3>\n
\n\n

Accessibility in Power Apps means designing canvas apps so users with different visual, hearing, motor, cognitive, or temporary needs can use the app successfully. This includes readable layouts, sufficient colour contrast, keyboard navigation, screen reader support, clear labels, and accessible controls.<\/p>\n\n<\/div>\n<\/div>\n

\n

Why is accessibility important in Dynamics 365?<\/h3>\n
\n\n

Dynamics 365 is often used for core business processes such as sales, service, operations, finance, and customer management. If the interface is difficult to read, navigate, or understand, users may struggle to complete work accurately. Accessibility improves usability, inclusion, adoption, and business process quality.<\/p>\n\n<\/div>\n<\/div>\n

\n

How can I check accessibility in Power Apps?<\/h3>\n
\n\n

Power Apps includes an Accessibility Checker that helps identify potential issues such as missing accessible labels, keyboard navigation problems, focus issues, missing captions, and screen reader concerns. Microsoft recommends using it to review canvas apps before release.<\/p>\n\n<\/div>\n<\/div>\n

\n

What are common accessibility issues in enterprise apps?<\/h3>\n
\n\n

Common issues include poor colour contrast, missing labels, confusing form layouts, unclear error messages, keyboard navigation gaps, invisible focus states, colour-only status indicators, inaccessible charts, and custom controls that do not work well with assistive technologies.<\/p>\n\n<\/div>\n<\/div>\n

\n

What accessibility standard should UK organisations consider?<\/h3>\n
\n\n

For UK public sector websites and mobile apps, GOV.UK guidance references WCAG 2.2 AA as part of meeting accessibility requirements. Private-sector organisations may not always be under the same specific public-sector regulation, but WCAG 2.2 remains a practical benchmark for improving digital accessibility<\/p>\n\n<\/div>\n<\/div>\n<\/div>\n<\/div>","protected":false},"excerpt":{"rendered":"

For many enterprise teams, accessibility still gets discussed too late. The app is already built.The forms are already configured.The dashboards are already approved.The workflow is already live.Then someone asks: can everyone actually use this? That is the wrong moment to discover accessibility gaps. On 21 May 2026, Global Accessibility Awareness Day puts digital access and […]<\/p>\n","protected":false},"author":44,"featured_media":237437,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","_lmt_disableupdate":"","_lmt_disable":"","jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[64],"tags":[194,195,196,197],"class_list":["post-237436","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-power-apps","tag-dynamics-365-accessibility","tag-gaad-enterprise-software","tag-inclusive-enterprise-apps","tag-power-apps-accessibility-checklist"],"modified_by":"mounika","jetpack_featured_media_url":"https:\/\/osmosys.co\/uk\/wp-content\/uploads\/sites\/6\/2026\/05\/1-3.png","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237436","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/users\/44"}],"replies":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/comments?post=237436"}],"version-history":[{"count":1,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237436\/revisions"}],"predecessor-version":[{"id":237438,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/posts\/237436\/revisions\/237438"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media\/237437"}],"wp:attachment":[{"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/media?parent=237436"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/categories?post=237436"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/osmosys.co\/uk\/wp-json\/wp\/v2\/tags?post=237436"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}