The only dirty solution I find is to create your own TextBlock control with its own corrected AutomationPeer. <\/strong>
\nIt will be based on the original TextBlockAutomationPeer but the IsControlElementCore method will always return true.
\nAs a bonus, I let commented a snippet which will expose the TextBlock only if an AutomationId is set on it.<\/p>\n

The code to write is really light. The real issue is that you have to update every TextBlock usage in the XAML of your application.
\n[csharp]
\npublic class AutomatisableTextBlock : TextBlock
\n{
\n protected override AutomationPeer OnCreateAutomationPeer()
\n {
\n return new AlwaysVisibleTextBlockAutomationPeer(this);
\n }
\n}<\/p>\n

\/\/The corrected AutomationPeer is based on the TextBlockAutomationPeer
\npublic class AlwaysVisibleTextBlockAutomationPeer : TextBlockAutomationPeer
\n{
\n public AlwaysVisibleTextBlockAutomationPeer(TextBlock t)
\n : base(t) { }<\/p>\n

protected override bool IsControlElementCore()
\n {
\n \/\/if (String.IsNullOrEmpty(GetAutomationId()))
\n \/\/ return false;
\n return true;
\n }
\n}
\n[\/csharp]<\/p>\n

Finally, the demo app XAML needs to be updated:
\n[xml]
\n<Grid>
\n <Grid.Resources>
\n <DataTemplate x:Key="ItemTemplate">
\n <local:AutomatisableTextBlock Text="{Binding }" \/>
\n <\/DataTemplate>
\n <\/Grid.Resources>
\n <ListBox ItemsSource="{Binding }"
\n ItemTemplate="{StaticResource ItemTemplate}" \/>
\n<\/Grid>[\/xml]<\/p>\n