diff --git a/components/status-message/spec/StatusMessage.stories.mdx b/components/status-message/spec/StatusMessage.stories.mdx
index d6132d54..56d524f0 100644
--- a/components/status-message/spec/StatusMessage.stories.mdx
+++ b/components/status-message/spec/StatusMessage.stories.mdx
@@ -46,7 +46,7 @@ Limit to important information, or when it’s changed. Overuse risks the messag
- Due for review 31 May 2021
+ Due for review
@@ -55,7 +55,7 @@ Limit to important information, or when it’s changed. Overuse risks the messag
- Due for review 31 May 2021
+ Due for review
@@ -67,7 +67,7 @@ Limit to important information, or when it’s changed. Overuse risks the messag
{ href: "#", text: "Review" },
{ href: "#", text: "Extend hold" },
]}>
- Due for review 31 May 2021
+ Due for review
@@ -99,7 +99,11 @@ If it’s about people, make sure your content is dynamic and personalised. Use
## Accessibility
-All users benefit from clear, visible notification messages which are presented in a consistent, predictable way. See the notifications guidance for more information
+All users benefit from clear, visible notification messages which are presented in a consistent, predictable way.
+
+If the status message component dynamically updates or appears on the page, for example as a result of user action, this needs to be announced to screen reader users. Consider using ARIA live region for this. See the notifications guidance for more information.
+
+If you are inlcuding the extra text or link sections then the main status should be marked up as a heading.
## Research